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!
Accepted Answer
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
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.