Kubernetes / Pods, Containers & Application Health
Explain a Running Pod that is not Ready
Running phase does not prove the application can serve traffic. Inspect readiness conditions and the configured probe before restarting the 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 describe pod web-0Read the result
The description exposes container readiness and recent probe events. A readiness failure normally changes traffic eligibility rather than restarting the container.
Resolve and verify
Compare the probe's endpoint, timing and dependency contract with actual application behavior. Correct the probe or underlying service and verify normal endpoints become ready.
Before changing production
Do not replace readiness checks with unconditional success to make a rollout appear healthy.