Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Hi.
I’m having issues with the Load Balancer in my Cluster/services.
I have created a certificate through the DO Control Panel (using Let’s Encrypt), used doctl compute certificate list to get the ID and attached to the service.beta.kubernetes.io/do-loadbalancer-certificate-id annotation from my Service.
It worked as it should. SSL responds correctly, but if I need to change the certificate from my LB, nothing happens. I put the ID from another certificate into the do-loadbalancer-certificate-id annotation but after saving, the old ID is still attached. If I remove, the certificate ID comes back.
I can’t find a way to change or revert the Certificate ID without deleting and creating a new Load Balancer, which it’s bad because my production app (for example) stops responding while the DNS doesn’t propagate yet.
As a workaround, I could create another service/LB with the correct certificate, but it’s a bit odd to do this.
Anyone had an issue like this?
Thanks!
1a3ca91ed97c49039b3e74fb7229fa
6efbf601fa8e49c884398e706c4672
f27857d3fd85405b8f50d9997c684d
petercorrea
ulope
josaf bodia
jediD83
rafaelri
Ben Buzbee
andreasAngler
Sharif