Question

Load Balancer gets assigned to default project, or end up not being assigned to any project

Posted August 29, 2021 129 views
Load BalancingKubernetes

As I was following this tutorial (https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-on-digitalocean-kubernetes-using-helm)

Every time I run the command

helm install nginx-ingress ingress-nginx/ingress-nginx --set controller.publishService.enabled=true

The Load Balancer gets created in my default project. Currently I have two projects, running that command creates a Load Balancer in the default project, the point is, my intention was not to create the Load Balancer in the default project.

If for example, I decide to delete my second project (not the default obviously), now I have only one project, if I restart the tutorial and run that command I end up with a Load Balancer not assigned to any project. It is pretty confusing. The Load Balancer does get create, if I go to the Networking tab, it is there, it even says to which project it is related (in [Project Name]). But if I go to the project page, in the resources list, the Load Balancer is not there and if I try to route traffic to that Load Balancer I get 404.

I followed the tutorial and ended up getting pretty much confused, I’m obviously doing something wrong as I don’t thing that this is a DO bug.

Submit an answer

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!