GCE Ingress

Google Cloud Ingress Controller connects Kubernetes application routes to Google Cloud load balancers. It reads Ingress resources and configures the external traffic path so users can reach the intended services. It is useful when operating that Google-managed routing model, especially on GKE. The load balancer has its own health checks and network requirements, so a service that works from inside the cluster may still be unavailable through its public endpoint.

Current guidance

The historical entry points to a malformed kubernetes/gce-gce URL. The verified project is kubernetes/ingress-gce, which implements the Google Cloud Ingress controller. Keep this identity separate from the retired community ingress-nginx controller and from a Google Cloud Gateway controller.

For GKE, begin with Google’s managed Ingress documentation. Determine the Ingress class, internal or external exposure, backend type and health-check behavior before editing manifests. A Service that answers within the cluster can still fail the load balancer health check. Check backend readiness, firewall permissions, certificates and the annotations or BackendConfig features actually used by your GKE version.

A migration to Gateway API should inventory URL maps, TLS ownership, redirects and application-specific annotations. Confirm the selected GatewayClass supports each required feature rather than translating the Ingress kind mechanically. Stage a separate endpoint and compare real request behavior before changing DNS. This review establishes the correct project and operating questions; it does not validate a self-managed ingress-gce installation or promise feature equivalence with another controller.