Watch Kubernetes Jobs and why they fail
A Job is only interesting when it's still running or when it failed. Kubius shows completions and parallelism, the pods a Job spawned and their logs, and the exit reason when one didn't finish - so a stuck or failing batch job is quick to diagnose.
Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later
Batch jobs, made legible
Completions & failures
See how many completions a Job needs, how many succeeded and how many pods failed - so progress and trouble are both obvious.
Logs from every attempt
Open the pods a Job created and read their logs, including from a failed attempt, where the error usually is.
Tune parallelism
Adjust parallelism and completions and apply - useful to speed up a big batch or dial it back.
OOM and exit codes
When a Job's pod died, Kubius surfaces the termination reason and exit code, including OOM kills, so failures make sense.
From CronJob to run
For scheduled work, jump from a CronJob to the Jobs it created and into their pods.
Live progress
Active, succeeded and failed counts update live as the Job runs.
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
Can I see why a Job failed?
Yes - Kubius shows the Job's failed pod count, and you can open those pods to read their logs and see the termination reason and exit code (including OOM kills).
Can I change parallelism or completions?
Yes - both can be adjusted and applied directly, without editing YAML by hand.
Does it link Jobs to their CronJob?
Yes. You can jump from a CronJob to the Jobs it spawned, and from a Job to its pods and their logs.
Do I need anything installed?
No - Kubius reads and updates Jobs through the Kubernetes API with your kubeconfig.