HTTPS forwarding rule removed from loadbalancer kubernetes

Good day sir/madam, In our kubernetes hosting, so far we have experience twice since we signed up, that our LoadBalancer sometime remove its HTTPS forwarding.

This make our environment not accessible from outside world. Our LoadBalancer droplet name/id: a37684cd4fe53437b8a89a2d18eb1de3

My question is, what happened? Is this situation normal? If this happen again, will we get notification?

Regards, Rizky Wahyudi

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.


DigitalOcean load balancers provisioned by Kubernetes are managed by the Cloud Controller Manager (CCM) running on the control plane.

Manual modifications to the load balancer through the cloud panel are overwritten by the CCM.

This occurs during the CCM’s reconciliation process.

This process runs to ensure that the load balancer is reflecting the state defined by the Kubernetes LoadBalancer service object.

For more information on how to prevent this please follow the steps here:



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up