Kore is a native macOS desktop app that brings a k9s-style, keyboard-driven experience to Kubernetes cluster management — without living in the terminal. It pairs a Rust backend (powered by kube-rs) with a React frontend (Vite + Tailwind + shadcn/ui) inside a lightweight Tauri v2 shell.
If you spend your day switching between kubectl, k9s, Lens, and your browser to manage clusters, Kore consolidates that workflow into a single, fast, keyboard-first app.
I totally get the concern giving an LLM 'write' access to a production cluster is definitely a scary thought.
To clarify: Kore is designed to be read-only by default. It’s an exploration and investigation tool, not a deployment or management engine. It uses the AI to help correlate data, explain complex status fields, and navigate the relationship between resources (like tracing why a Service isn't hitting its Endpoints).
Since the tool does not perform any apply, patch, or delete operations, there is no risk of the AI 'hallucinating' a destructive command that would actually impact the cluster infrastructure.
i'm sure apply support is just one PR away, why shy away from it? embrace!
i encourage it - the faster and the more colorful this makes infrastructures around the world blow up and burn down, the quicker we might actually learn how to be resilient in presence of the ultimate chaos monkey.
Kore is a native macOS desktop app that brings a k9s-style, keyboard-driven experience to Kubernetes cluster management — without living in the terminal. It pairs a Rust backend (powered by kube-rs) with a React frontend (Vite + Tailwind + shadcn/ui) inside a lightweight Tauri v2 shell.
If you spend your day switching between kubectl, k9s, Lens, and your browser to manage clusters, Kore consolidates that workflow into a single, fast, keyboard-first app.
can't wait to wreck my infrastructure in ways and with speed not conceivable before!
I totally get the concern giving an LLM 'write' access to a production cluster is definitely a scary thought. To clarify: Kore is designed to be read-only by default. It’s an exploration and investigation tool, not a deployment or management engine. It uses the AI to help correlate data, explain complex status fields, and navigate the relationship between resources (like tracing why a Service isn't hitting its Endpoints).
Since the tool does not perform any apply, patch, or delete operations, there is no risk of the AI 'hallucinating' a destructive command that would actually impact the cluster infrastructure.
i'm sure apply support is just one PR away, why shy away from it? embrace!
i encourage it - the faster and the more colorful this makes infrastructures around the world blow up and burn down, the quicker we might actually learn how to be resilient in presence of the ultimate chaos monkey.