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?

I tried the following approach to resolve the issue with keeping the same DOLB its IP and so on. Looks like works for me.

1. Setup your DOLB manually
2. Change service type to NodePort, provide prefered nodePort values.
3. Provide your externalIP for DOLB, you can probably provide it using properties
4. On your DOLB setup forwarding rules, in my case is TCP on port 443 TCP on port 30443 TCP on port 80 TCP on port 30080
5. On yor DOLB setup health checks, in my case is tcp://0.0.0.0:30080
6. Enjoy your Load Balancer and not-changing IP you can use to configure DNS.

apiVersion: v1
kind: Service
metadata:
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp
    service.beta.kubernetes.io/aws-load-balancer-type: nlb
  name: kong-proxy
  namespace: kong
spec:
  ports:
    - name: proxy
      **nodePort: 30080**
      port: 80
      protocol: TCP
      targetPort: 8000
    - name: proxy-ssl
      **nodePort: 30443** 
      port: 443
      protocol: TCP
      targetPort: 8443
  externalIPs: 
    - 111.111.111.111 # IP of your DO manually created load balancer 
  selector:
    app: ingress-kong
  **type: NodePort**

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!

Same issue as https://www.digitalocean.com/community/questions/how-to-set-static-ip-for-loadbalancer-in-kubernetes

DO?

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.