To enable LoadMaster to Kubernetes communication, the LoadMaster must have Kubernetes API access. To enable this, follow the steps below in the LoadMaster UI:

1. In the main menu, go to Virtual Services > Kubernetes Settings.
2. Click Choose File.
3. Browse to and select your Kube Config file.
   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.
   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: 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: This allows the LoadMaster to communicate with Kubernetes.
4. Click Install.
5. Once the Kube Config file is successfully installed, some information is populated in the Contexts section.
   Note: The Name, Cluster, and User are shown.
6. Select the relevant K8S Operations Mode.
   Note: For further details on each mode, including instructions on how to configure each mode in Kubernetes, refer to the Service Mode and Ingress Mode section.
   Note: For further details on each mode, including instructions on how to configure each mode in Kubernetes, refer to the Service Mode and Ingress Mode section.
   Note: For further details on each mode, including instructions on how to configure each mode in Kubernetes, refer to the Service Mode and Ingress Mode section.
7. Select the Namespace to Watch.
   Note: 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.
8. Optional: Set the Ingress Watch Timeout in seconds.

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.