Loading page
Jump from a failing pod to its logs or a live shell in one motion. Stream output, search it, download it, or open a PTY when reading is not enough.
$ kubectl logs -f api-7d9f8c5b6
02:14:03 INF readiness probe ok
02:14:04 INF connected to postgres
waiting for input
A real PTY, opened from the same pod row.
KubeView/logs · exec$ kubectl logs -f api-7d9f8c5b6
02:14:08 WRN readiness probe failed: HTTP probe failed with statuscode: 502
02:15:02 ERR dial tcp 10.0.2.19:5432: connect: connection refused
02:15:03 ERR upstream request failed
02:16:12 resolved postgres to 10.0.2.19
_
Same pod, same context. A real PTY through the local Go engine.
$ ls /app
$ env | grep API
$ getent hosts postgres
Move from the grid to a streaming log without copying a pod name.
Interactive sh or bash runs through the Go engine's PTY.
Filter the stream or save the full log for a postmortem.
The readiness probe starts failing after a config change. Logs and a shell are one click away from the pod that needs them.
Readiness fails
The pod stays Running, but the service removes it from the endpoint list.
Read the logs
The last lines show dial tcp 10.0.2.19:5432: connection refused.
Open a shell
getent hosts postgres returns the old service IP. The rollback starts.
From symptom to root cause without leaving KubeView.
No agent, no sidecar, no dashboard to configure. The desktop app talks directly to the Kubernetes API with the credentials already on your machine.
Open a pod from the grid or the deep inspector drawer.
Stream every container, or start a terminal in the running container.
Search, copy, download, and switch containers without moving apps.
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.