Cannot access Kubernetes Cluster after deleting Load Balancer having custom Ingress

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.

  • Should a managed cluster always have a DigitalOcean load balancer?
  • I see the cost of a managed cluster starts at 10/month. Is the cost of the load balancer included?

Thanks in advance.

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 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:

  type: LoadBalancer
    app: nginx-example
    - 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:

Regards, Bobby