I am trying to get a fairly basic set up working wiht K8s:
- simple UI host that serves up some HTML
- NGinx in front of it that proxies to the simple UI host when a certain domain is hit
The result being that when I navigate to somedomain.com NGinx should proxy the request to the UI host.
I have deployed my UI host into the cluster and have also configured NGinx in the cluster
So - couple questions
Do I need a DO LB sat in front of all this? If i don’t need a load balancer where do I find the IP for the cluster to point the DNS at?
Do I need an nginx-ingress or is plain old nginx ok?
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!
This comment has been deleted
Disclaimer: I work at DigitalOcean on the managed Kubernetes offering.
Hey Wayne,
Do I need a DO LB sat in front of all this? If i don’t need a load balancer where do I find the IP for the cluster to point the DNS at?
Strictly speaking, you do not need a DO LB. However, one key advantage of using it is that it’d be robust towards node replacements. In general, you should not rely on IP addresses being fixed in the (any) cloud, especially not with Kubernetes where a cluster upgrade may replace some or all of your nodes. A DO LB set up through a Kubernetes Service gives you a layer of stability by not binding to IP addresses specifically. You could also come up with a custom solution to manage Droplet IP addresses on your own with regards to load-balancing and external accessibility, but that’s an investment you’d have to make. You would find your Kubernetes worker node (droplet) IP addresses on your DigitalOcean cloud dashboard (the web UI).
Do I need an nginx-ingress or is plain old nginx ok?
nginx-ingress is vanilla Nginx combined with a so-called Ingress controller; that is, a little service that is able to process Kubernetes Ingress objects and provide external access to your Kubernetes applications. It does so by watching over changes made on Ingress objects and reconfiguring Nginx accordingly.
While you could use nginx-ingress (or another Ingress controller, like HAProxy’s, Envoy’s, or Traefik), it’s probably easier in your case to just run vanilla nginx and point external traffic at it. Again, a DO LB would be a viable option to accomplish the routing part.
Hope this helps!
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 AI-native businesses
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.