Kubestellar Console: A Dashboard for Multi-Cluster Fleet Management

If you've ever tried to manage multiple Kubernetes clusters across different environments, you know the pain. You're hopping between contexts, juggling kubectl commands, and hoping you don't accidentally apply a config to the wrong cluster. It's exhausting, and it's easy to make mistakes.

Enter Kubestellar Console. It's a web-based UI built on top of the Kubestellar project — a platform for managing Kubernetes workloads across many clusters at scale. The console gives you a clear, visual way to see what's happening across your fleet without relying on terminal gymnastics.

What It Does

Kubestellar Console is a frontend dashboard that connects to a Kubestellar backend. Once set up, it shows you a unified view of your workload deployments, cluster health, and resource usage across all your managed clusters. You can browse which workloads are running where, inspect individual cluster status, and get a high-level picture of your multi-cluster infrastructure.

Under the hood, it uses Kubernetes-native APIs and the Kubestellar custom resources to present data that would otherwise require custom scripting or multiple terminal windows. It's a UI layer, but a well-designed one.

Why It's Cool

The obvious win here is visibility. Without a console, you'd need to manually query each cluster or stitch together metrics from Prometheus, Grafana, or custom dashboards. Kubestellar Console gives you a single pane of glass that works out of the box with Kubestellar's data model.

What's clever is how it leverages existing Kubernetes concepts. You're not learning a new API or a proprietary config language. If you already understand namespaces, deployments, and cluster management, the console feels familiar. It also supports role-based access control (RBAC) so you can safely share the view with a team without exposing credentials.

Another nice touch: it's built with a React frontend and a Go backend, making it easy to extend if you need custom views or integrations. The code is clean and well-organized, which is rare for early-stage open source tools.

How to Try It

You can run it locally with Docker or deploy it into your own cluster. The repo has clear instructions in the README. Here's the quickstart:

git clone https://github.com/kubestellar/console.git
cd console
docker compose up

Then open http://localhost:3000 in your browser. You'll need a Kubestellar backend running somewhere (check the main Kubestellar repo for setup). If you don't have a fleet ready, you can still explore the UI with a demo mode.

For production use, there's a Helm chart available. The documentation covers both options.

Final Thoughts

Multi-cluster Kubernetes management is still a messy space, but tools like Kubestellar Console are making it less painful. If you already run Kubestellar or plan to, this console is a no-brainer addition. It saves you time, reduces mistakes, and gives you a nice visual overview without requiring a full observability stack.

If you're just curious about multi-cluster patterns, the codebase is also worth a look as a clean example of building a Kubernetes-aware UI.

Follow us on X: @githubprojects