Kubernetes / Pods, Containers & Application Health
Investigate ImagePullBackOff before changing registry credentials
A pull failure can involve an absent tag, authorization, DNS, rate limiting or platform incompatibility. Preserve the exact runtime event.
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
Container waiting reasons and events usually identify the attempted image and a more specific pull error. Backoff itself is only retry behavior.
Resolve and verify
Check the exact registry, image reference, supported architecture and approved pull-secret association. Correct the demonstrated image or access issue and observe a fresh attempt.
Before changing production
Do not paste registry tokens into tickets, use an unverified replacement image or disable registry TLS validation.