Question

Load balancer name keept getting reset

In my project I have 2 Kubernetes clusters, production and development. For each clusters I have a load balancer named production and development respectively.

Often when I look back, I notice the name of the development load balancer is renamed to its original value (the initially generated hash name). This issue does not exist for production.

What could be causing this?

Subscribe
Share

Having the same issue as well. I change settings in regards https and add a ssl cert, and it resets back to default.

I am having exactly the same issue… furthermore, it reset the loadblanacer settings.

Mine is 5 days old now, it has resets 3 times already.

I’ve the same issue.

The issue exists on the development load balancer only. This cluster is actually slightly newer than production.

Hey,

Can you provide some details about your cluster version? Newer DOKS clusters version of the cloud controller manager should allow for you to change the name of the LB, and leave it alone.

Are your development and production LB’s both experiencing this, or just development? Can you try renaming any other LB’s on that development cluster and see if they also get renamed?

Regards,

John


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!

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.

Accepted Answer

This can be set with the service.beta.kubernetes.io.do-loadbalancer-name annotation on the ingress controller.

When using the ingress-nginx Helm chart, use --set-string 'controller.service.annotations.service\.beta\.kubernetes\.io/do-loadbalancer-name=your-value'

This comment has been deleted