Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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.
Accepted Answer
Hi there!
Each node will have its own public IP. The control plane API will be managed for you but exposed via a URL made up of your cluster’s UUID.
These IP’s will change as nodes are upgraded and recycled. The IP’s of the nodes will change as they are replaced with new nodes. Floating IP’s will not re-attach to new nodes that replace them as the new nodes have no awareness of the nodes they are replacing.
To expose services that are running in the cluster I would recommend creating a LoadBalancer type service. You can find documentation on exposing a service via LB here: https://www.digitalocean.com/docs/kubernetes/how-to/add-load-balancers/
I would recommend exposing your traefik service as a DO LB. This LB would be a consistent public IP for your requests to use that would always route to Traefik. Then using ingress rules you can distribute traffic accordingly to your services.
Hope this helps!
Regards,
John