The Ingress Controller is not installed on the LoadMaster by default. You can easily install it by following these steps:

  1. In the LoadMaster User Interface (UI), go to Virtual Services > Kubernetes Settings.
  2. Click Install.
  3. Wait for the installation to complete and click OK on the confirmation message.
  4. Reboot the LoadMaster to activate all required add-ons - System Configuration > System Administration > System Reboot > Reboot.

After rebooting, you can use the Kubernetes Settings configuration page to enable the LoadMaster Kubernetes integration.

Note: For LoadMasters deployed in AWS or Azure in a High Availability pair, please ensure that the add-ons are installed on both devices.
Note: LoadMaster users (apart from the default admin bal user) must be assigned the All Permissions option in their user permissions to be permitted access to modify Kubernetes settings in the LoadMaster.

Kube Config

This allows the LoadMaster to communicate with Kubernetes.

The default location for the Kube Config file is ~/.kube/config, for example, if you are using the Azure Cloud Shell you can access this using /home/<YourName>/.kube/config using the Download File option at the top of the Cloud Shell window.

Note: If using Minikube, it is recommended to embed the certificates used for authentication inside the kubeconfig file. This can be done with the following command in Minikube:minikube config set embed-certs true
Note: If the backup of one LoadMaster is restored to another LoadMaster, it is recommended to upload the Kube Config file separately to the restored LoadMaster.

Once the Kube Config file is successfully installed, some information is populated in the Contexts section. The Name, Cluster, and User are shown.

K8S Operations Mode

Determines the Ingress Controller mode of operation (Ingress or Service). "K8S" is used in the Virtual Service list to indicate a Virtual Service that is under Kubernetes control. For further details on each mode, including instructions on how to configure each mode in Kubernetes, refer to the Progress Kemp Ingress Controller for Kubernetes Feature Description.

Namespace to Watch

The K8s namespace to watch. All namespaces are watched if this field is unset. You can only filter on either a single name space or all name spaces. There is no capability to select multiple name spaces at this time.

Ingress Watch Timeout (secs)

The Ingress Controller watch timeout (in seconds). Valid values range from 30 - 900.

When configured correctly, details on the Kubernetes Nodes and relevant objects (Ingress Objects with an ingress class specification of "kempLB" and Service Objects labeled "kempLB:Enabled") are shown at the bottom of the screen.

For further details, refer to the Progress Kemp Ingress Controller for Kubernetes Feature Description.