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!
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.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
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