// the find
kubetail-org/kubetail
Real-time logging dashboard for Kubernetes. View logs in a terminal or a browser. Run anywhere - desktop, cluster, docker.
Kubetail merges logs from multi-container Kubernetes workloads into a single chronological timeline and tracks pod lifecycle events so the stream stays coherent as ephemeral containers come and go. It talks directly to the K8s API — no log forwarder, no sidecar, no external service — so it works immediately against any cluster your kubeconfig points at. It is aimed at developers and ops teams who want a better kubectl logs without adding pipeline infrastructure.
The direct K8s API approach is the right call: data never leaves your cluster, nothing to configure, nothing to break. The container lifecycle tracking is what actually makes this useful — kubectl logs quietly drops lines as pods restart, and Kubetail handles that correctly by watching lifecycle events and stitching the timeline together. Distribution coverage is genuinely impressive for a 1700-star project: Ubuntu PPA, Fedora COPR, AUR, SUSE OBS, Alpine testing, Krew, Nix flakes, Winget, Chocolatey — 15+ package managers in CI. The cluster agent is Rust with a purpose-built rgkl crate for forward/backward log file streaming, which suggests they thought carefully about the read path rather than just wrapping kubectl.
Log search requires installing the optional Kubetail Cluster API into your cluster — without it you get grep and time-range filtering only. This two-tier capability model means most users hit the ceiling fast and then face a 'now install stuff in your cluster' conversation. No historic log support exists and it is step 6 on a roadmap where steps 3–7 are all unstarted, so if a pod is gone the logs are gone and there is no path to that changing soon. The development environment requires a running K8s cluster plus Tilt to work on most of the codebase, making contributions genuinely high-friction. The Go+Rust+React+GraphQL+pnpm+Tilt stack is also a lot of surface area for a log viewer — the architectural ambition is visible in the repo but so is the complexity cost.