A Pod stays in Init:ImagePullBackOff and the main app container image is known-good. What is the most likely focus for diagnosis?
Select an answer to reveal the explanation.
Short Explanation
If the warm-up act’s costume never arrives, the show never starts—even if the headliner’s outfit is fine. Init:ImagePullBackOff points at the init image or its pull access, not the Service type.
Full Explanation
Pods blocked in an init image-pull failure cannot proceed to application containers. Diagnosis centers on the init container’s image reference and registry authentication, separate from a healthy app image. Scaling replicas, readiness probes, and Service types do not skip or cure init image pull errors.