Loading page
Onboard a kind cluster or a production EKS context without editing environment files. KubeView indexes contexts, resolves auth plugins, and tells you exactly where a connection breaks.
Context connected
KubeView/connection pathNetwork
Endpoint reachable
Auth
token refreshed
TLS
Handshake verified
RBAC
Namespace allowed
KubeView indexes standard kubeconfig paths and every context inside them.
Exec plugins such as aws-iam-authenticator and gke-gcloud-auth-plugin work out of the box.
Network, auth, TLS, and RBAC checks point to the exact failing hop.
A new EKS context refuses to connect. The four-stage check turns a vague timeout into the exact failed hop.
Network
The API endpoint resolves and the TLS handshake starts.
Auth
aws-iam-authenticator returns an expired token. TLS and RBAC wait behind it.
Fix
Refresh the credential, run diagnostics again, and the context turns green.
A connection problem is diagnosed without editing kubeconfig by hand.
No agent, no sidecar, no dashboard to configure. The desktop app talks directly to the Kubernetes API with the credentials already on your machine.
Use standard paths, drop in a folder, or paste raw YAML.
The Go engine resolves certificates, tokens, and exec plugins locally.
If a context refuses to connect, the four-stage check shows why.
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.