IstioKubernetes

Galley Endpoint Discovery Failure

critical
reliabilityUpdated Jan 7, 2026

Galley component fails to discover pod endpoints for services, preventing Istio from routing traffic correctly. This manifests as istio_galley_endpoint_no_pod errors and results in 503 upstream connection failures.

How to detect:

Monitor istio_galley_endpoint_no_pod for services that have endpoints without corresponding pods. Check istio_galley_runtime_state_type_instances to verify Galley is processing service configurations. Look for istio_galley_process_cpu_seconds spikes indicating Galley is under load.

Recommended action:

Verify that pod selectors in Service definitions match pod labels. Check that namespace has istio-injection enabled label. Restart Galley pods if stale state is suspected. Review istio_galley_runtime_strategy_timer_resets and istio_galley_runtime_strategy_timer_max_time_reached to identify timing issues in configuration processing.