I Built LogDeck: A Desktop App for Kubernetes Pod Logs
retained text
Hey all. I spend a lot of time debugging apps on Kubernetes, and my workflow was always `kubectl logs -f | grep`, scrolling through thousands of lines to find the one error that matters. So I built LogDeck, a small desktop app focused only on reading logs. **What it does:** * Live logs with colored levels (INFO/WARN/ERROR…) and a volume histogram; drag on it to filter a time range. * Groups repeated errors into one card with count and time range (IDs and numbers normalized). * Side-by-side view with the previous container (`--previous`) when a pod is crash-looping. * Search with regex, exclude filters and presets; also opens saved log files. **How it talks to the cluster:** * It runs the `kubectl` you already have, with your kubeconfig. No agent, nothing installed in the cluster, no account, no telemetry. * Read-only: only `get`, `logs`, `auth can-i` and `version` are allowed; any other verb is blocked in code. The only exception is a container terminal (`kubectl exec`), which opens only when you click it. **How it compares:** k9s and stern are great, and I still use them. This is for when you want a GUI focused on just logs, not a full cluster manager like Lens or Headlamp. **Honest notes:** It’s Electron, so it’s not tiny. There’s an optional “explain these errors” button that uses AI, but it’s off unless you configure it (Claude Code CLI or a local model). macOS, Linux and Windows (Microsoft Store). MIT licensed: [https://github.com/wisecort/LogDeck](https://github.com/wisecort/LogDeck) It’s early, and I’d really like to know what’s missing or broken. Things like multi-pod tailing or other log formats are the kind of feedback I’m after.
document fetched 2026-10-14 00:37 · canonical https://reddit.com/r/kubernetes/comments/1x5b5k8/i_built_logdeck_a_desktop_app_for_kubernetes_pod