AI-powered multi-cluster Kubernetes dashboard with guided install missions for 250+ CNCF projects.

Live Demo | Contributing

curl -sSL https://raw.githubusercontent.com/kubestellar/console/main/start.sh | bash

Opens at localhost:8080. Deploy into a cluster with deploy.sh (--openshift, --ingress <host>, --github-oauth, --uninstall).

kc-agent connects console.kubestellar.io to your local clusters:

brew tap kubestellar/tap && brew install --head kc-agent   # macOS
go build -o bin/kc-agent ./cmd/kc-agent && ./bin/kc-agent  # Linux (Go 1.24+)

1. Create a GitHub OAuth App

   • Homepage URL: http://localhost:8080
   • Callback URL: http://localhost:8080/auth/github/callback

2. Clone the repo (if you haven't already):

   git clone https://github.com/kubestellar/console.git
   cd console

3. Create a .env file in the repo root (console/.env):

   GITHUB_CLIENT_ID=your-client-id
   GITHUB_CLIENT_SECRET=your-client-secret
   

4. Start the console:

   ./startup-oauth.sh

Open http://localhost:8080 and sign in with GitHub. For Kubernetes deployments, pass --github-oauth to deploy.sh instead.

To enable feedback and GitHub-powered features (nightly E2E status, community activity), go to Settings in the console sidebar and add a GitHub personal access token under GitHub Token.

The console can also create GitHub issues programmatically via the /issue page. To enable this, add a Personal Access Token to .env:

FEEDBACK_GITHUB_TOKEN=your-github-personal-access-token

The token needs a classic repo scope or a fine-grained token with Issues: Read & Write. Without it, issue submission returns 503 Issue submission is not available.

1. Onboarding — Sign in with GitHub, answer role questions, get a personalized dashboard
2. Adaptive AI — Tracks card interactions and suggests swaps when your focus shifts (Claude, OpenAI, or Gemini)
3. MCP Bridge — Queries cluster state (pods, deployments, events, drift, security) via kubestellar-ops and kubestellar-deploy
4. Missions — Step-by-step guided installs with pre-flight checks, validation, troubleshooting, and rollback
5. Real-time — WebSocket-powered live event streaming from all connected clusters

See the full Architecture documentation on the KubeStellar website.

• console-kb — Knowledge base of guided installers for 250+ CNCF projects and solutions to common Kubernetes problems
• console-marketplace — Community-contributed monitoring cards per CNCF project
• kc-agent — Local agent bridging the browser to kubeconfig, coding agents (Codex, Copilot, Claude CLI), and MCP servers (kubestellar-ops, kubestellar-deploy)
• claude-plugins — Claude Code marketplace plugins for Kubernetes
• homebrew-tap — Homebrew formulae for KubeStellar tools
• KubeStellar — Multi-cluster configuration management

Console uses AI tools (GitHub Copilot, Claude Code) to accelerate development. Quality is maintained through layered feedback loops — every PR triggers the same automated checks regardless of author, and continuous monitoring catches what PR checks miss.

• Before commit: TypeScript build + Go build + 5 post-build safety checks + lint
• Before merge: nil-safety, ts-null-safety, array-safety, API contract, Playwright E2E, coverage gate, TTFI performance, CodeQL, Copilot code review, UI/UX standards scanner, visual regression
• Visual regression: 18 UI components documented as Storybook stories with theme support. Playwright captures screenshots and diffs against baselines on every PR that touches UI components.
• After merge: Targeted Playwright tests run against production (console.kubestellar.io); failures reopen the original issue
• Continuous: Hourly coverage (12 shards), 4x daily QA, nightly E2E, nightly security scanning, real-time GA4 error tracking, UI/UX standards nightly scan

When a regression class is identified, a maintainer adds an automated check to the earliest possible loop. See docs/AI-QUALITY-ASSURANCE.md for the full breakdown.

Apache License 2.0 — see LICENSE.