I want to expose my service deployed to k8s cluster and I have Ingress controller for such purpose. It works fine, but as known IP addresses allocates by Ingress are ephemeral(at least in GKE), which means you can’t use them to bind such IPs to your domain during DNS configuration.
So, couple of questions I have:
- Are IPs allocated by Ingress controller ephemeral in Digitalocean?
- If so, is it possible to point Floating IP address to Ingress controller?
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.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
They are pushing you to use LBs. And those LBs are quite expensive (without a possibility to solve this issue with some alternative). So, their k8s is more like a toy at the moment.
Hey friend,
I asked internally about this and thought this answer from Javi might be helpful:
“What I’ve done is use a service to bind a LB as a service in front of an Ingress Controller ( I used Nginx Ingress ) and that let me keep the public LB IP.”
There is not currently a way to use a floating IP for this.
Jarland