GKE - how to attach static ip to internal load balancer

2/5/2020

I want to connect service from one GKE cluster to another one. I created service as a internal load balancer and I would like to attach a static ip to it. I created my service.yml

apiVersion: v1
kind: Service
metadata:
  name: ilb-service
  annotations:
    cloud.google.com/load-balancer-type: "Internal"
    kubernetes.io/ingress.global-static-ip-name: es-test
  labels:
    app: hello
spec:
  type: LoadBalancer
  selector:
    app: hello
  ports:
  - port: 80
    targetPort: 8080
    protocol: TCP

However after apply -f when I check the service the load balancer ingress looks like this:

status:
  loadBalancer:
    ingress:
    - ip: 10.156.0.60

And I cannot connect using the static ip. How to solve it ?

EDIT:

After suggestion I changed the yml file to:
apiVersion: v1
kind: Service
metadata:
  name: ilb-service
  annotations:
    cloud.google.com/load-balancer-type: "Internal"
  labels:
    app: hello
spec:
  type: LoadBalancer
  selector:
    app: hello
  ports:
  - port: 80
    targetPort: 8080
    protocol: TCP
  loadBalancerIP: "xx.xxx.xxx.xxx" -- here my static ip

Service now looks like it:

spec:
  clusterIP: 11.11.1.111
  externalTrafficPolicy: Cluster
  loadBalancerIP: xx.xxx.xxx.xxx
  ports:
  - nodePort: 31894
    port: 80
    protocol: TCP
    targetPort: 8080
  selector:
    app: hello
  sessionAffinity: None
  type: LoadBalancer
status:
  loadBalancer: {}

And I still cannot connect

-- Clyde Barrow
google-cloud-networking
google-cloud-platform
google-kubernetes-engine

1 Answer

2/5/2020

You won't use the annotation for the internal IP. Instead, just specify the IP address you want to use (not by name) in the spec.loadBalancerIP field allows you to specify a numeric IP address to assign to the loadBalancer. Make sure the IP is not in use anywhere else and is within the same subnet as your cluster.

EDIT

To clarify the last statement: If you have the internal IP reserved as a static IP, that IP is no longer available, it is considered "in use" by the static reservation. To assign the IP to an internal LoadBalancer, the IP must not be reserved nor can it be in use.

This is not made clear, but it is because of how the GCP controller created internal loadbalancers that it is unable to use an already reserved IP address.

-- Patrick W
Source: StackOverflow