In DO Kubernetes, how to change the CNI from default Cilium to say Calico
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there,
I don’t think there’s an official guide on changing the CNI in DOKS. Since it’s a managed service, swapping out the default Cilium for something like Calico might not be supported and could lead to issues. It’s probably best to stick with the default Cilium CNI unless you have a strong reason to switch.
If you really need the flexibility of choosing your own CNI, a self-hosted Kubernetes cluster might be the way to go. This way, you have full control over the networking stack and can use Calico or any other CNI of your choice:
For clarification or to see if there’s any workaround, I’d recommend reaching out to DigitalOcean support:
- Bobby.