Question
Kubernetes - Cilium Routes Cluster Traffic through Public Interface
- Posted on November 12, 2022
- DigitalOcean Managed KubernetesKubernetesNetworking
Asked by elekube
Hi,
I recently created a DigitalOcean Kubernetes cluster. However, Cilium is routing node-to-node traffic via the public interfaces on the Droplet, instead of the internal interfaces (10.x.x.x).
This makes doing certain things, like using the PROXY protocol on load balancers and setting trusted IP ranges on NGINX Ingress difficult, since when autoscaling, new nodes might have completely random and unpredictable IPs.
Is there a DigitalOcean approved method to update Cilium to route traffic properly that won’t be overwritten when DO does managed updates/upgrades?
Thank you
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.
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hi,
After a lot of research, I discovered that managed Kubernetes agents are automatically added to a Firewall (in the Networking tab) which prevents all access.
As a result, I can remove the trusted IP settings. I would still prefer that network traffic occur on the private network, but it’s not as much of a show stopper.
Thanks