I work as a backend developer and Kubernetes is part of my normal day. What kept annoying me was how even simple debugging ended up spread across terminal tabs and tools. I’d check a namespace, open a pod, read logs, look at events, edit some YAML, port-forward or exec into a container, and then often find out the real problem was kubeconfig, RBAC or auth.
Rune is what I built for that workflow. It’s a native macOS client written in Swift that keeps everything around one Kubernetes problem close together: YAML, events, full or unified logs across pods, exec, port-forwards and auth troubleshooting. It’s keyboard-first, with a command palette and quick jumps. It talks to the Kubernetes API with its own client, including exec and port-forward, so it doesn’t need kubectl. There’s no backend or proxy for cluster data, and no analytics or telemetry.
2.7 shipped recently, and pod status now matches kubectl, including sidecars and init containers. 3.0 is coming soon with a reworked UI, pinnable tabs and a much faster terminal.
Rune is also one of three native Mac tools I’ve built that hand work to each other. I can export a bundle of logs and YAML from Rune and open it in QuikZip without extracting it. I edit the files in Inkline and save them straight back into the archive, then apply them again in Rune.
I work as a backend developer and Kubernetes is part of my normal day. What kept annoying me was how even simple debugging ended up spread across terminal tabs and tools. I’d check a namespace, open a pod, read logs, look at events, edit some YAML, port-forward or exec into a container, and then often find out the real problem was kubeconfig, RBAC or auth.
Rune is what I built for that workflow. It’s a native macOS client written in Swift that keeps everything around one Kubernetes problem close together: YAML, events, full or unified logs across pods, exec, port-forwards and auth troubleshooting. It’s keyboard-first, with a command palette and quick jumps. It talks to the Kubernetes API with its own client, including exec and port-forward, so it doesn’t need kubectl. There’s no backend or proxy for cluster data, and no analytics or telemetry.
2.7 shipped recently, and pod status now matches kubectl, including sidecars and init containers. 3.0 is coming soon with a reworked UI, pinnable tabs and a much faster terminal.
Rune is also one of three native Mac tools I’ve built that hand work to each other. I can export a bundle of logs and YAML from Rune and open it in QuikZip without extracting it. I edit the files in Inkline and save them straight back into the archive, then apply them again in Rune.
Links: Website: https://viktornyberg.com Mac App Store: https://apps.apple.com/us/app/runeapp/id6762515322?mt=12 GitHub: https://github.com/compilererrors/Rune Direct download (Apple silicon, supports exec-plugin auth): https://github.com/compilererrors/Rune/releases/tag/v2.7-bui...