Kubernetes / Services, DNS & Traffic Routing
Map an EndpointSlice address back to its actual Pod and node
A service incident can affect only one published endpoint. Identify that endpoint before restarting the whole workload.
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
Target references, addresses, node information and conditions help map traffic to the selected backend. Slices can be multiple and change during rollout.
Resolve and verify
Correlate the failing backend with its Pod logs, listener and node path. Repair the specific dependency and verify endpoint eligibility and request success.
Before changing production
Do not edit controller-managed EndpointSlices manually to hide an unhealthy Pod.