Konnectivity Agent

Konnectivity Agent in Thalassa Cloud Kubernetes

The Konnectivity Agent is a critical component in Thalassa Cloud Kubernetes, enabling secure and reliable communication between the Kubernetes API server and cluster nodes. This component is essential for handling Kubernetes API traffic, ensuring that cluster components can communicate effectively regardless of underlying network constraints.

How Konnectivity Agent Works

Thalassa Cloud Kubernetes operates with a separated control plane, which runs outside the cluster and does not have direct access to the cluster Pod network or VPC networking. Because of this, it is necessary to deploy the Konnectivity solution from the Kubernetes project.

Konnectivity Agent establishes secure tunnels between the Kubernetes API server and the Kubernetes cluster, ensuring that essential functionality such as log retrieval, exec commands, and API extensions operates seamlessly within the cluster deployment.

Deployment and Configuration

Thalassa Cloud Kubernetes automatically installs and manages the Konnectivity Agent as part of the control plane setup. Do not uninstall the component, as this will break some functionality from the Kubernetes cluster. Thalassa Cloud Kubernetes will automatically restore the Konnectiivty Agent deployment should it have been undeployed. This may take several minutes.

Checking if the Konnectivity Agent is Running

To verify if the Konnectivity Agent is active in your cluster, run:

kubectl get pods -n kube-system | grep konnectivity-agent

If the agent is running correctly, you should see an active pod listed.

Troubleshooting

If the agent is not running or experiencing issues:

  • Ensure that network policies allow outbound connections from worker nodes to the control plane.
  • Ensure that VPC firewall rules or security groups allow outbound connections from the worker nodes to the control plane.
  • Restart the agent by deleting the pod and letting Kubernetes recreate it:
    kubectl delete pod -n kube-system -l app=konnectivity-agent
  • Check the logs for errors:
    kubectl logs -n kube-system -l app=konnectivity-agent