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?
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!
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
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 SMBs
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.