Case

Kubernetes: ImagePullBackOff

The cluster cannot pull the image. Events and registry access are checked to restore deployments.

Case Summary

  • ProblemPods fail because the image cannot be pulled (wrong tag or missing auth).
  • SolutionValidate image/tag exists and configure imagePullSecrets if registry is private, then redeploy.
  • Toolskubectl describe/events · registry credentials · imagePullSecrets
  • OutcomeSuccessful image pull, pods start normally.

Commands used (examples)

kubectl get pods -n <ns>
kubectl describe pod <pod> -n <ns>
kubectl logs <pod> -n <ns> --previous
kubectl get events -n <ns> --sort-by=.lastTimestamp | tail
systemctl status <service> --no-pager
journalctl -u <service> -n 200 --no-pager