Removing kube-proxy

Some CNI plugins support replacement of kube-proxy in favor of internal better-optimized solutions.

Please note that if you deploy your SKS clusters with a pre-configured CNI plugin, this is already handled by our SKS orchestrator and does not apply to your situation.

An example of support replacement of kube-proxy is a custom deployment of Cilium with “strict” kube-proxy replacement.

In this specific situation, you would ideally remove kube-proxy before any pods are scheduled in the cluster. To achieve this, you can provision your cluster without kube-proxy:

• using the Terraform provider SKS resource with the enable_kube_proxy attribute set to false
• using the Exoscale CLI with the --enable-kube-proxy flag set to false when creating your cluster