Image pull errors happen when Kubernetes cannot download the container image for your deployment. You may see ImagePullBackOff or ErrImagePull in status or events.
- Explains why the app has no ready pods.
- Points to image, tag, registry, and pull-secret problems.
- Helps you decide whether to fix the image reference or registry credentials.
- The app URL returns 502 or 503.
- Deployment events mention image pull failures.
- The pod status shows
ImagePullBackOff or ErrImagePull.
- Access to deployment logs and events.
- Knowledge of the expected image name and tag.
- Registry access if the image is private.
Screenshot Required
- Open the deployment detail page.
- Check events for
ImagePullBackOff, ErrImagePull, unauthorized, or not found messages.
- Confirm the image registry, repository, and tag are correct.
- Confirm the image tag exists in the registry.
- For private images, confirm the registry credentials are valid.
- Redeploy or rebuild after fixing the image or credentials.
- Assuming the tag exists because the image name is correct.
- Using stale credentials after rotating a registry password.
- Checking app logs when the container never started.
- Events are more useful than app logs for image pull failures.
- If a Git build succeeded but deploy cannot pull, check the registry project and namespace pull secret.