Hi, what’s the structure (i.e. architecture) of your Kubernetes resources? Are you using a LoadBalancer in regards to your service resource definition? If this is the case, then you should never hard code an IP address here. Next, If you have created a DNS record that has an associated IP address, then I would create a Kubernetes Ingress resource using either Nginx or Traefik that sets the domain and not the IP.

e.g.

kind: Ingress
apiVersion: extensions/v1beta1
metadata:
  name: "foo"
  namespace: production
spec:
  rules:
    - host: some.example.com
      http:
        paths:
          - path: /
            backend:
              serviceName: some_service_1
              servicePort: 80

Note: The above is using Traefik apiVersion.

Well, I wish that the above information helps you and happy hacking.

–

Think different and code well,

-Conrad

Hi there,

Looking at a LB service you should see they are provisioned with the loadbalancer id annotation.

To reuse a current already provisioned LB. You can use that annotation on the service that you want to take over the LB:

kubernetes.digitalocean.com/load-balancer-id: xxxxxx-blah-UUID-here-xxx

Please note that you should not have a LB being managed by two clusters as they will overwrite each others configurations.

Hope this helps!