GKE Ingress Fix for Unreachable Services

Repair GKE ingress routing when the external load balancer never reaches the service.

April 22, 2026•1 min read

#gcp#gke#ingress

Problem

Traffic reaches the GKE load balancer IP but the application is still unreachable.

Root Cause

The backend service health checks fail because the service port or readiness path is incorrect.

Fix

Code

kubectl describe ingress web-gateway -n platform
kubectl get svc web -n platform -o yaml
kubectl get endpoints web -n platform
kubectl patch deployment web -n platform --type merge -p '{"spec":{"template":{"spec":{"containers":[{"name":"web","readinessProbe":{"httpGet":{"path":"/healthz","port":8080}}}]}}}}'

Result

Health checks pass, backend endpoints become healthy, and the ingress serves traffic.

Ad Slot

Replace with Google AdSense or partner placement when monetization is enabled.

Premium Slot

Reserve this space for premium runbooks, downloadable templates, or paid incident checklists.