kubestellar-console
Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills
- License 许可
- Apache-2.0
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- kubestellar-console
- risk
- critical
- tags
- [ "kubernetes", "multi-cluster", "mcp", "dashboard", "cncf", "devops", "observability" ]
- tools
- [ "claude", "cursor", "gemini", "codex" ]
- author
- kubestellar
- plugin
- { "setup": { "docs": "https://github.com/kubestellar/console#quick-start", "type": "manual", "summary": "Requires kc-agent binary (brew tap kubestellar/tap && brew install kc-agent)" } }
- source
- community
- license
- Apache-2.0
- category
- devops
- date_added
- 2026-04-27
- description
- Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills
- source_repo
- kubestellar/console
- source_type
- community
- license_source
- https://github.com/kubestellar/console/blob/main/LICENSE
03 SKILL.md 正文
KubeStellar Console
Overview
KubeStellar Console is an open-source multi-cluster Kubernetes dashboard (CNCF project) with AI-powered operations. It ships with kc-agent, an MCP server that bridges coding agents to kubeconfig and Kubernetes APIs, plus 10+ built-in agent skills for development, testing, and operations.
When to Use This Skill
- Use when managing multiple Kubernetes clusters across edge and cloud
- Use when you need AI-assisted Kubernetes troubleshooting and debugging
- Use when running performance tests, cache compliance checks, or CI debugging on a Kubernetes dashboard
- Use when integrating with CNCF projects (Argo, Kyverno, Istio, and 20+ others)
How It Works
Step 1: Install kc-agent
brew tap kubestellar/tap && brew install kc-agent
Step 2: Start the MCP server
kc-agent
This bridges the active kubeconfig context to any MCP-compatible coding agent. Do not start it from a cluster-admin or write-capable context unless the user explicitly accepts that risk.
Step 3: Use built-in agent skills
The project ships with agent skills accessible via CLAUDE.md and AGENTS.md:
- @perf-test — Dashboard performance testing and TTFI analysis
- @cache-test — Card cache compliance testing (IndexedDB warm return)
- @nav-test — Navigation performance testing
- @ui-compliance-test — Card loading compliance (8 criteria, 150+ cards)
- @ci-status — CI pipeline monitoring and status checks
- @rca — Root cause analysis for CI/test failures
- @tdd — Test-driven development workflow
- @k8s-debug — Kubernetes debugging and troubleshooting
Key Features
- Multi-cluster management across edge and cloud
- Real-time streaming observability
- 20+ CNCF project integrations (Argo, Kyverno, Istio, etc.)
- GitHub OAuth authentication
- Supply chain security (SBOM, SLSA)
- SQLite WASM caching with stale-while-revalidate pattern
- 15+ themes with dark/light mode
Security & Safety Notes
- Critical risk:
kc-agentbridges your active kubeconfig context to MCP-compatible agents. If that context carries cluster-admin, write permissions, or secret read access, agents inherit those capabilities. - Do not rely on RBAC objects alone: creating a ServiceAccount or ClusterRoleBinding does not change the credentials
kc-agentuses. Startkc-agentonly after switchingKUBECONFIG/context to dedicated least-privilege credentials and verifying them. - Recommended read-only scope: avoid
resources='*', because it includes sensitive objects such as Secrets. Prefer an explicit non-secret resource list and verify access before starting the MCP server:kubectl create serviceaccount kc-agent -n default kubectl create clusterrole kc-agent-readonly \ --verb=get,list,watch \ --resource=pods,services,deployments.apps,replicasets.apps,statefulsets.apps,daemonsets.apps,namespaces,nodes,events,configmaps kubectl create clusterrolebinding kc-agent-readonly \ --clusterrole=kc-agent-readonly \ --serviceaccount=default:kc-agent kubectl auth can-i get secrets --as=system:serviceaccount:default:kc-agent kubectl auth can-i list pods --as=system:serviceaccount:default:kc-agent - The first
can-icommand must returnno; the second should returnyes. Then create or select a kubeconfig that actually authenticates as that ServiceAccount before runningkc-agent. - Do not expose
kc-agenton a public network without authentication. - Review SECURITY-AI.md for prompt injection and agent drift mitigations.
Limitations
- This skill requires an external binary (
kc-agent) installed separately via Homebrew. - Do not treat agent output as a substitute for environment-specific validation or expert review.
- Stop and ask for clarification if required permissions or safety boundaries are unclear.
Links
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.