Question

How-to deliver a new public IP to a k8s cluster so a k8s service that requires UDP port (Bind DNS server) can use it?

How-to deliver a new public IP to a k8s cluster so a k8s service that requires UDP port (Bind DNS server) can use it?

I know how to expose an IP address in K8s services by defining ‘externalIPs’ attribute. It just won’t work unless the IP address is available to the cluster.

I wonder if I can attach a Floating IP to a K8s service. So far I was not able to. I need an equivalent solution, somehow.

I even tried DO’s load balancer but I could not configure it for UDP traffic.

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Hi @superherointj

You are correct. Unfortunately, our LB’s do not support UDP traffic at this time.

The node IP addresses should not be relied upon to stay consistent. Whenever a node is replaced or upgraded the IP will be changed.

To accomplish this you would likely need to set up an external proxy to keep track of the current node IP’s and forward traffic accordingly. Because of these limitations you may have better luck hosting your UDP service on our standard droplet product.

Regards,

John Kwiatkoski Senior Developer Support Engineer - Kubernetes