Question
How does one point a domain to a Kubernetes cluster?
- Posted on August 23, 2019
- DigitalOcean Managed KubernetesDigitalOceanKubernetes
Asked by Joseph Palacio
I understand how kubernetes ingresses work. I understand kubernetes services are used to expose one’s deployed service(s). What I don’t understand is how to get traffic into my cluster with a DigitalOcean managed Kubernetes.
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.
This comment has been deleted
No you do not need to create one first. The managed kubernetes logic will do that for you. Once it is created, you can check the LB’s IP that it was assigned(via kubectl or the DO cloud panel) and setup your domain to resolve to that LB IP.
Let me know if you have any additional questions.
Regards,
John Kwiatkoski Senior Developer Support Engineer
Hi there!
Most commonly, people use services of type ‘LoadBalancer’ to get traffic into the clusters:
https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#configuration-file
Once a load balancer service is created our cloud controller manager that runs on your master will notice the new service is of type ‘LoadBalancer’ and provision a DO load balancer to be pointed at your DOKS nodes at the NodePort specified or generated by the service. Now any traffic that hits your LB’s IP will be routed as follows(with a few exceptions):
User Request -> DO LB -> kubernetes node -> service -> pod
That LB will have an external-facing IP where you can point all you traffic that belongs to that service. Users often create their ingress controller service as the loadbalancer type and then use ingress rules to have the ingress controller distribute traffic. This prevents users from needing a individual LB for each service.
https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/
Regards,
John Kwiatkoski Senior Developer Support Engineer