Kubernetes / Pods, Containers & Application Health
Investigate a Pending Pod through scheduler evidence
A Pod can remain Pending because no node satisfies its requirements, or because setup has not completed. Read the conditions and scheduling events.
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 shows current state, conditions and recent events available for this Pod. Event retention is limited and the displayed message may be a consequence rather than the first cause.
Resolve and verify
Match unschedulable reasons with requests, taints, affinity and storage requirements. Correct the demonstrated constraint through the workload owner and verify scheduling and readiness.
Before changing production
Do not remove all placement rules or repeatedly recreate the Pod before understanding why it cannot run.