Question

How to reuse DO LoadBalancer previously created through Kubernetes?

Posted November 15, 2018 4.5k views
Load BalancingKubernetes

Hi,

when creating a Kubernetes cluster and using a load balancer to host any public service, its easy to imagine that there would be anything going terribly wrong with the cluster. In that case I would like to create a new cluster and reuse the LoadBalancer to still have the same Public IP has before. Is there a possibility to request a specific load balancer name to be reused within the service definition? Or is elastic ip support for LoadBalancers planned?

This would increase fix possibilities in cases where there are infrastructure issues.

Dennis

1 comment
  • Any updates on this issue? We need to use some way of fixing the public ip of nginx-ingress controller, so that even on re-installing helm chart after purging, we don’t need to make changes to DNS records.

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.

×
10 answers

Hi Dennis,

Thanks for your question. I’m Tyler, the product manager for our Load Balancer product. At this point in time, it’s not possible to re-use an existing LB. It has to be generated as a new LB in order to get registered in k8s properly and things to be routed correctly. This wouldn’t be impossible, per se, but it’s not something we’re looking to add soon, unfortunately.

I will say that we are considering working on adding floating IP support to Load Balancers, which completes part of your request. This would be something that would likely happen in mid-2019.

Hi, I’m analyzing k8s infrastructure in DO to start using it as a permanent solution. I’m facing this issue now and it doesn’t look good to not be able to reuse a previous IP address. If the cluster has any issues and there’s a need to regenerate it (or maybe there’s a need to do a cleanup), the traffic will be “dead” until DNS change takes effect for the new load balancer. Is there any fix planned for this situation?

Thank you for the transparency.

I have the same situation, wanting to reuse existing loadbalancer when rebuilding cluster, or at least reuse the same public IP. Could we get an update on how the work is going with adding floating IP support to Load Balancers?

@tylerdo Any updates on floating IP support for Load Balancers?

Hi! Any news about this? We have the same situation here, we need re-use an created load balancer and don’t see the possibility to attach a Floating IP at Load Balancers.

Thanks!

Any progress on this, please? We’re facing the same issue.

Have you tried this.

[...]
using the kubernetes.digitalocean.com/load-balancer-id annotation.
[...]
You can have digitalocean-cloud-controller-manager manage an existing load-balancer by creating
a LoadBalancer Service annotated with the UUID of the load-balancer. Do not do this while it is
being managed by another cluster, or the digitalocean-cloud-controller-managers will make
conflicting modifications to the load-balancer.
  • @gosi Adding the “kubernetes.digitalocean.com/load-balancer-id” annotation to the LB service does force the cluster to use an existing load balancer, but when you delete the LB service, the controller automatically removes the LB too (regardless of whether it existed before the cluster was created). So, this doesn’t seem to help.

It would be great to be able to make sure that the LB IP address is reserved for our Organization and can be reused any time. Any Solution (floating IP?)works for us, but please make it possible.

In some cases we can’t control the Domain settings directly so the downtime could be significant if we have to switch to another IP for any unforeseen reason.

Submit an Answer