External Ingress Load Balancer with Europenean Static IP Address

[peter_iglaev]

Hey, we configured ingress to use regional IP address instead of global one and face with the issue

Error syncing to GCP: error running load balancer syncing routine: <ingress-lb-name> does not exist: the given static IP name <static-external-ip-address-name-regional> doesn't translate to an existing static IP.

We need to configure External Ingress with static IP address located in Europe.

Ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-ingress-eu
  namespace: web
  annotations:
    # kubernetes.io/ingress.global-static-ip-name: <static-external-ip-address-name-global>
    kubernetes.io/ingress.regional-static-ip-name: static-external-ip-address-name-regional> 
    networking.gke.io/managed-certificates: managed-cert
    kubernetes.io/ingress.class: "gce"
spec:
  defaultBackend:
    service:
      name: web-service
      port:
        number: 80

[francislouie]

Hi peter_iglaev,

Welcome to Google Cloud Community!

According to the documentation, when using GKE Ingress with an external HTTP(S) load balancer (GCELB), you must use a global static IP address. However, if you're using the NGINX Ingress controller, it's possible to use a reserved regional static IP address instead. You can refer to the official documentation for guidance on how to configure a static IP with NGINX Ingress.

Here’s an example of the output :

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.