How to Investigate a Kubernetes Service That Routes Traffic to an Old Pod

A Service may keep sending requests to a pod that should have been removed if endpoint readiness, selector labels, rollout state, or service mesh discovery is stale. Users may see intermittent behavior as old and new replicas coexist.

What to check

Inspect EndpointSlices, pod labels and readiness, deployment rollout, termination grace period, service selectors, and mesh or proxy caches. Compare the target pod IDs with the current deployment revision.

Recommended next step

Correct the selector or readiness behavior and allow graceful connection draining. Verify all endpoints after rollout and monitor requests for stale application versions.

How Informatix Systems can help

Informatix Systems provides Kubernetes and container platform engineering services. We can assess the affected environment, trace the problem through its dependencies, and help plan a practical improvement. Contact us with the system involved, when the issue began, and non-sensitive error details.