Find out why a pod is stuck in Pending
A Pending pod is a scheduling problem - not enough CPU or memory, a taint it doesn't tolerate, a node selector that matches nothing, or a volume that won't bind. Kubius shows the FailedScheduling events and the requests, nodes and constraints behind them.
Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later
Everything the scheduler is telling you
FailedScheduling events
The scheduler's own message - 'insufficient cpu', 'had untolerated taint', 'no nodes available' - shown against the pod, newest first.
Requests vs capacity
See the pod's CPU and memory requests next to what the nodes can actually offer, so a too-big request is obvious.
Taints, affinity, selectors
Node selectors, affinity rules and the tolerations the pod carries are rendered clearly - a mismatch is easy to spot.
Unbound volumes
A PersistentVolumeClaim that can't bind keeps a pod Pending; Kubius surfaces the PVC and its status so you catch it.
The nodes in play
Inspect the nodes and their pressure and cordon state to see whether there's simply nowhere for the pod to land.
Back to the workload
Jump to the owning Deployment or StatefulSet to adjust requests, tolerations or the node selector at the source.
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
Why is my pod stuck in Pending?
Almost always scheduling: the cluster can't place it. Common causes are resource requests bigger than any node's free capacity, a taint the pod doesn't tolerate, a node selector or affinity that matches no node, or a PersistentVolumeClaim that won't bind. Kubius shows the FailedScheduling events and all of these in one view.
Where do I see the scheduler's reason?
Kubius lists the pod's events - including the scheduler's FailedScheduling message - newest first, right on the pod, so you see exactly why it couldn't be placed.
Can it show unbound PVC problems?
Yes. If a pod is Pending because a volume won't bind, Kubius surfaces the referenced PersistentVolumeClaim and its status.
Do I need Prometheus or agents?
No - it reads pod status, events and node capacity from the Kubernetes API with your kubeconfig.