A new Deployment for a court-calendar UI stays in ImagePullBackOff. Which cause is most consistent with that status?
Select an answer to reveal the explanation.
Short Explanation
ImagePullBackOff means the node never got the picture off the shelf—typo’d name/tag or no key to the private gallery. Fix the reference or the imagePullSecrets. Probes and emptyDir drama happen after a successful pull.
Full Explanation
ImagePullBackOff (and related ErrImagePull) occurs when the kubelet cannot retrieve the container image—commonly due to an incorrect repository/name/tag or missing/invalid credentials for a private registry (imagePullSecrets). Probe failures, volume capacity, and HPA replica bounds affect running or scaling behavior after images are present, not the pull failure itself.