Service has no ready endpoints because backing pods aren't ready. Fix by checking pod readiness, fixing application health, and verifying endpoint selectors.
Fixes ENDPOINT_NOT_READY
kubectl get endpoints -n <namespace> <service-name>kubectl get endpoints -n <namespace> <service-name>Endpoint not ready, no endpoints available for service
On this page
Endpoints represent the ready pod IPs backing a service. When no endpoints exist, traffic can't reach any pods.
kubectl get endpoints -n <namespace> <service-name>kubectl get pods -n <namespace> --show-labelskubectl get pods -n <namespace>Debug and fix pod startup or health check.
kubectl get service -n <namespace> <name> -o yaml | grep selector:Use kubectl get endpointslices to see endpoints in newer Kubernetes.