Loading page
See what changed before you touch the cluster. KubeView compares local YAML with live resources, shows the diff, checks RBAC with a dry run, and applies only when you confirm.
# deployment.yaml
- replicas: 3
+ replicas: 5
image: ghcr.io/acme/api:2.4.1
KubeView/review change# deployment.yaml
- replicas: 3
+ replicas: 5
image: ghcr.io/acme/api:2.4.1
strategy: RollingUpdate
Compare local manifests with live resources, review the diff, then apply only after a dry-run and explicit confirmation.
Desired vs live
Classify every local manifest as in sync, changed, missing, or error.
Review before apply
Inspect desired and live YAML side by side before anything changes.
Dry-run and RBAC
Validate the manifest and your permissions before the apply gate.
A local replicas change is waiting. KubeView shows exactly what will move before anything reaches production.
deployment.yaml changed
The API deployment is at 3 replicas in the cluster and 5 in the worktree.
Service missing
The service manifest is not live. RBAC allows patch; two warnings are listed.
Apply after review
The diff is clean. Apply waits for explicit confirmation.
The change lands with no surprise fields.
No agent, no sidecar, no dashboard to configure. The desktop app talks directly to the Kubernetes API with the credentials already on your machine.
Choose a local directory or Git worktree containing Kubernetes YAML.
KubeView scans the source and compares it with live resources.
Only after a successful dry-run and explicit confirmation does the change land.
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.