The LoadMaster Ingress Controller for Kubernetes enables a LoadMaster Virtual Service to be used to publish access to Kubernetes applications. This enables application server pools in published Virtual Services to dynamically update when Pods running on a Kubernetes platform are added or removed from a proxied service object. This provides a convenient way for managing the connection between the Load Balancer and Container network for connections into Kubernetes (commonly referred to as North-South Traffic).

Because the LoadMaster operates outside of Kubernetes, the Ingress Controller provides a convenient way for managing end points for either Containerized or Monolithic Applications or a combination of both through the same device.

You first need to install the Ingress Controller on the LoadMaster. Once installed, you can enable this functionality in Service or Ingress mode.

This functionality provides the following capabilities:

  • Automated mapping of Kubernetes Service or Ingress object configurations to LoadMaster Virtual Services and SubVSs

  • Support for mapping Kubernetes annotations to Virtual Service attributes

  • Automated addition and deletion of Real Servers as a result of changes in Kubernetes (for example, scale up or scale down operations)