By lewislbr
I’ve recently created a managed Kubernetes cluster, deployed several services with a custom ingress, and I could access correctly the app at the IP provided by the ingress service.
Then I found out a load balancer was created automatically by DigitalOcean, and thinking I already had the ingress I didn’t need it so I deleted it. Now the app is no longer accessible.
I don’t really understand the connection between the cluster and the load balancer.
Thanks in advance.
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!
Hi there,
As the load balancer is a separate resource, it is billed separately.
In case that you have a Kubernetes service created with type LoadBalancer, for example:
spec:
type: LoadBalancer
selector:
app: nginx-example
ports:
- name: http
protocol: TCP
port: 80
targetPort: 80
Once you apply this to your cluster, this will automatically spin up a Managed DigitalOcean Load Balancer under your account.
For more information, I could suggest taking a look at the first answer here:
https://www.digitalocean.com/community/questions/how-does-one-point-a-domain-to-a-kubernetes-cluster
Regards, Bobby
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.