Find out why a pod can't pull its image
ImagePullBackOff usually comes down to a wrong image name, a missing registry credential or a rate limit - and the reason is sitting in the pod's events. Kubius surfaces the pull error, the image reference and the pod events in one live view.
Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later
The whole pull failure, in one place
The exact pull error
ErrImagePull, ImagePullBackOff, manifest-not-found or unauthorized - Kubius shows the message the kubelet reported, so you know which it is.
Image and tag, front and centre
See the full image reference the pod is trying to pull - a typo, a wrong tag or a missing registry host is usually obvious once it's on screen.
Pull secrets, checked
See which imagePullSecrets the pod references, so you can tell a missing or wrong registry credential from a bad image name.
Events, newest first
The Failed / BackOff events are listed against the pod in order, so the pull failure and its cause are right there.
Fix it at the source
Jump to the owning Deployment or Job to correct the image or the pull secret in the template, not just the pod.
No agents needed
Everything is read live from the Kubernetes API with your kubeconfig - nothing to deploy into the cluster.
Simple, one-time pricing
Pay once. No subscription.
One-time licence from €49 - no subscription. 14-day free trial, no card required.
Free 14-day trial · macOS Sonoma (14) or later · No agents, nothing to install in-cluster
Questions, answered
How does Kubius help with ImagePullBackOff?
It puts the pull error, the exact image reference, the pod's imagePullSecrets and the relevant events in one live view, so you can tell whether it's a wrong image name, a missing registry credential or a rate limit - then fix the template it came from.
Can it tell a bad image name from a missing credential?
Yes - the kubelet's error message plus the referenced pull secrets make it clear whether the image can't be found or the pull was unauthorized.
Do I need anything installed in the cluster?
No. Kubius reads pod status and events straight from the Kubernetes API using your existing kubeconfig.
Can I fix the problem from Kubius?
You can jump to the owning workload and edit its YAML to correct the image or pull secret; applying manifests is part of Kubius Pro, included in the trial.