# Disable kube-proxy

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][cilium-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][terraform-provider-no-kube-proxy] SKS resource with the `enable_kube_proxy` attribute set to `false`
- using the [Exoscale CLI][exo-cli] with the `--enable-kube-proxy` flag set to `false` when creating your cluster

[cilium-kube-proxy-replacement]: https://docs.cilium.io/en/v1.18/network/kubernetes/kubeproxy-free/#kubeproxy-free
[terraform-provider-no-kube-proxy]: https://registry.terraform.io/providers/exoscale/exoscale/latest/docs/resources/sks_cluster#enable_kube_proxy-1
[exo-cli]: https://github.com/exoscale/cli