Loading page
KubeView keeps informer-backed watches open on the resources you care about. Pods appear, restart, and move without a refresh loop, so the grid always reflects the cluster.
Informer-backed · no polling
KubeView/watch streamInformer-backed watches push pod changes the moment they land. No refresh button.
No refresh loop
State arrives through informer and watch streams, not a timer.
Moment-of-change state
See restarts, phase changes, and scheduling updates as they land.
Stable under load
Delta updates keep the UI responsive on large clusters.
No agent, no sidecar, no dashboard to configure. The desktop app talks directly to the Kubernetes API with the credentials already on your machine.
The Go engine starts watches for the resources KubeView is showing.
Informer caches turn Kubernetes watch events into compact deltas.
The UI merges changes without a full reload or a manual refresh.
A deployment replaces its pods across the namespace. The grid follows every intermediate state without a refresh loop.
Rollout starts
A new ReplicaSet appears. Two old pods move to Terminating.
Pods land
ContainerCreating rows fill in with node names and readiness states.
State settles
Six Running pods. The old ReplicaSet drops to zero without a page reload.
The view matches the cluster at every step.
The surfaces are designed to hand off to each other, so you can move from symptom to root cause without changing tools.
Bring your kubeconfig. KubeView handles discovery, auth, live watches, and the troubleshooting workbench, all on your machine.