Kubernetes / Services, DNS & Traffic Routing
Investigate a Service with no ready EndpointSlice addresses
A matching Pod can be excluded from ordinary service traffic when readiness is false. Inspect endpoints rather than only counting running Pods.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app get endpointslices -l kubernetes.io/service-name=web -o yamlRead the result
EndpointSlice conditions, ports and target references show the currently published routing information. Special Service settings can alter readiness publication.
Resolve and verify
Match each endpoint with its Pod readiness and actual listener. Repair the underlying probe or application dependency and verify eligible addresses appear.
Before changing production
Do not publish unready endpoints merely to hide a broken application startup path.