|
1 | | -# KubeStellar Console Roadmap |
2 | | - |
3 | | -This document outlines the planned direction for KubeStellar Console. It is a living document and will be updated as priorities evolve based on community feedback, user needs, and ecosystem changes. |
4 | | - |
5 | | -## Completed Milestones |
6 | | - |
7 | | -### v0.1 — Foundation (Q3 2025) |
8 | | -- Multi-cluster dashboard with real-time health monitoring |
9 | | -- Helm release tracking across clusters |
10 | | -- Pod, deployment, and event monitoring cards |
11 | | -- Demo mode with MSW mock data for offline usage |
12 | | -- GitHub OAuth authentication |
13 | | -- Dark/light theme support |
14 | | - |
15 | | -### v0.2 — Intelligence Layer (Q4 2025) |
16 | | -- AI-powered missions system with Claude and kagent integration |
17 | | -- Community missions browser with console-kb knowledge base |
18 | | -- Contributor rewards system with leaderboard and coin economy |
19 | | -- 80+ dashboard cards covering CNCF ecosystem |
20 | | -- GPU monitoring cards (overview, inventory, utilization, reservations) |
21 | | -- OPA, Kyverno, Falco, and Trivy security cards |
22 | | -- ArgoCD application monitoring |
23 | | -- Drag-and-drop dashboard customization with card catalog |
24 | | - |
25 | | -### v0.3 — Scale & Operations (Q1–Q2 2026) |
26 | | -- **Console Studio** — Visual dashboard builder with AI card generation |
27 | | -- **Mission Control** — Guided CNCF project deployment with Flight Plan blueprint, phased launch, and AI-assisted cluster assignment; dry-run mode and kind cluster E2E tests |
28 | | -- **Orbital Maintenance** — Automated cluster maintenance missions with scheduling |
29 | | -- **Benchmark streaming** — Real-time vLLM/llm-d performance data via Google Drive with hardware leaderboards |
30 | | -- **GPU namespace drill-down** — Per-GPU-type, per-node allocation views |
31 | | -- **Workload import dialog** — YAML, Helm, GitHub, and Kustomize import support |
32 | | -- **NPS survey system** — In-app Net Promoter Score feedback collection |
33 | | -- **VCluster and KubeVirt** cards for virtualized workloads |
34 | | -- **Marketplace** — Community card preset marketplace with 45+ CNCF project templates |
35 | | -- **OpenSSF Scorecard improvements** — Signed releases, SLSA provenance, scoped workflow permissions |
36 | | -- 160+ total dashboard cards |
37 | | -- Nightly and weekly automated releases with Helm OCI chart publishing |
38 | | -- Comprehensive Auto-QA workflows for code quality, governance, and UI consistency |
39 | | -- Contributor leaderboard with GitHub-synced rewards |
40 | | -- **AI Missions UX** — Message edit/resend, microphone input, scroll-to-bottom, draft click-to-open, history toggle panel, mission sort by activity, retry on failure, response cancellation |
41 | | -- **Auth hardening** — GA4 telemetry on auth failure paths (SSE 401, WS token missing, agent token failure, session refresh), agentFetch migration for all kc-agent calls, HS256-only JWT parsing (TAG-Security fix) |
42 | | -- **kc-agent API expansion** — `/nvidia-operators`, `/events/stream` SSE, `/federation/detect`, agent token bridging to frontend |
43 | | -- **Responsive container-query rollout** — Phase 3a/3b across 63 files: responsive skeleton grids, flex-wrap in CNCF status cards |
44 | | -- **Test infrastructure** — Coverage from 0% to 91%: 10,000+ unit tests, 12-shard parallel coverage, coverage regression guard with auto-issue, post-merge Playwright verification against production |
45 | | -- **Code quality automation** — UI/UX standards scanner with Storybook and Playwright visual regression, post-build vendor safety checks, MSW catch-all for unmocked routes |
46 | | -- **Backend refactoring** — Monolith splits: sqlite.go (3,321 → 8 files), server_http.go/server_ai.go/server_operations.go into domain handlers, CardWrapper.tsx into 4 sub-components; 609 fmt.Sprintf calls converted to structured slog fields |
47 | | -- **ArgoCD ApplicationSet** integration with security fixes |
48 | | -- **Saved Filter Sets** — Snapshot all filters into named presets; merged Project Selector and Filter Panel into single dropdown |
49 | | -- **Learn dropdown** — Auto-populated from YouTube playlist with video tutorials |
50 | | -- **Claude Code GitHub Action** — AI-assisted PR review and issue triage via Claude Opus 4.6 |
51 | | - |
52 | | ---- |
53 | | - |
54 | | -## 2026 Milestones Overview |
55 | | - |
56 | | -The 2026 roadmap focuses on three major delivery themes: |
57 | | - |
58 | | -1. **v0.4 AI-Native Observability** (Q3 2026) — First-class support for AI/ML workloads, Drasi reactive pipelines, and kagent integration |
59 | | -2. **Stellar subsystem GA** (Q3–Q4 2026) — Graduate the persistent AI runtime from alpha to production with finalized CRDs and adoption validation |
60 | | -3. **CNCF incubation preparation** (Q4 2026) — Complete governance documentation, security audit, and community maturity metrics required for TOC application |
61 | | - |
62 | | -This roadmap is informed by community feedback, adoption metrics, strategic partnerships, and the branch stability covenant for v0.3 recovery. |
63 | | - |
64 | | ---- |
65 | | - |
66 | | -## Near-Term (Q3 2026) — v0.4 AI-Native Observability |
67 | | - |
68 | | -This milestone crystallizes near-term roadmap items into a cohesive theme: establishing KubeStellar Console as the canonical AI/ML workload visibility and operations layer for Kubernetes. |
69 | | - |
70 | | -### Core Scope |
71 | | - |
72 | | -- **llm-d stack monitoring** — First-class support for llm-d inference serving: EPP routing, model endpoint health, autoscaler status, disaggregated serving topology |
73 | | -- **Drasi reactive pipelines** — Real-time change-feed dashboard for Drasi continuous queries, sources, and reactions across deployment modes (drasi-server, drasi-platform, CRD-based) |
74 | | -- **kagent/kagenti integration** — Full agent lifecycle management through MCP-compatible interfaces |
75 | | - |
76 | | -### Quality & Testing |
77 | | - |
78 | | -- **Nightly E2E expansion** — Automated end-to-end testing across all 8 llm-d deployment guides on OpenShift |
79 | | -- **Marketplace v2** — Require live data hooks, unified controls, demo data, and install links for all card presets; community review process |
80 | | - |
81 | | -### UX & Accessibility |
82 | | - |
83 | | -- **i18n completeness** — Eliminate all hardcoded English strings; prepare for community localization contributions |
84 | | -- **Accessibility audit** — Replace remaining `window.confirm()` dialogs, add ARIA labels, keyboard navigation for all interactive elements |
85 | | -- **GA4 UX funnel** — Measure conversion from landing to agent install to first mission; identify and fix drop-off points |
86 | | -- **Component consistency** — Migrate remaining raw HTML elements to shared UI components (Button, Modal, Dialog); standardize modal visibility patterns |
87 | | - |
88 | | -### Community Health |
89 | | - |
90 | | -- **Adopters program** — Populate ADOPTERS.MD with confirmed production users; define maturity tiers (install-mission vs. production deployment) |
91 | | -- **Contributor onboarding** — Establish PR triage SLA, define `ai-needs-human` escalation path, and publish contributor guide update; see `docs/plans/PR-TRIAGE-SLA.md` |
92 | | -- **Adoption metrics** — Replace all `TBD` fields in `docs/adoption-metrics.md` with real measurements before any CNCF application |
93 | | - |
94 | | -### Tech Debt Unblocking Strategy |
95 | | - |
96 | | -As the codebase scales past 160+ dashboard cards and 10,000+ unit tests, technical debt items that were previously deprioritized ("hold" status) now represent scaling risks. This section defines the unblocking strategy to address accumulated tech debt before it impacts delivery velocity. |
97 | | - |
98 | | -**Priority 1: Performance & Scalability** |
99 | | -- **Card render optimization** — Audit and fix cards with >500ms initial render time; establish performance budgets per card type |
100 | | -- **Cache eviction policy** — Implement LRU eviction for SQLite WASM cache to prevent unbounded growth; target <50MB cache size |
101 | | -- **Test parallelization** — Reduce CI test suite runtime from current baseline; investigate Jest worker memory limits |
102 | | - |
103 | | -**Priority 2: Code Health** |
104 | | -- **TypeScript strict mode** — Enable `strict: true` incrementally, starting with new files; eliminate remaining `any` types in card components |
105 | | -- **Dependency updates** — Unblock Vite 6, React 19, and Tailwind 4 upgrades currently held due to breaking changes; allocate dedicated sprint |
106 | | -- **Bundle size** — Audit and tree-shake unused dependencies; target <2MB initial JS bundle (currently ~2.8MB) |
107 | | - |
108 | | -**Priority 3: Developer Experience** |
109 | | -- **Storybook coverage** — Achieve 80% component coverage in Storybook (currently ~40%); prioritize cards with complex state |
110 | | -- **E2E test stability** — Fix flaky Playwright tests in `nightly-e2e` workflow; define retry/timeout standards |
111 | | -- **Documentation debt** — Update outdated API docs in `pkg/api/`, particularly for Stellar subsystem endpoints |
112 | | - |
113 | | -**Execution Model** |
114 | | -- Allocate 20% of each sprint cycle to tech debt work (approximately 1 issue per developer per 2-week sprint) |
115 | | -- Tag tech debt issues with `tech-debt` label and priority tier (`p1-perf`, `p2-health`, `p3-dx`) |
116 | | -- Track tech debt ratio (tech debt issues / total issues) as a key health metric; target <15% |
117 | | -- Block new feature work if tech debt ratio exceeds 25% or any P1 item is open >30 days |
118 | | - |
119 | | -**Branch Stability Covenant (effective immediately):** Main branch must remain green at all times. A post-merge integration smoke gate (combining TS build, auth smoke, and workflow startup checks) is required before new feature PRs are merged. See issue [#17756](https://github.com/kubestellar/console/issues/17756) for tracking. |
120 | | - |
121 | | ---- |
122 | | - |
123 | | -## Mid-Term (Q4 2026 – Q1 2027) — Stellar GA & CNCF Preparation |
124 | | - |
125 | | -Strategic milestones for production hardening, ecosystem integration, and CNCF readiness. |
126 | | - |
127 | | -- **Stellar subsystem GA** — Graduate the Stellar persistent AI runtime from alpha to GA: finalize CRD versioning (v1 stability), complete Mission Operator test coverage, publish upgrade path documentation, and achieve at least one confirmed non-demo deployment. GA criteria tracked in [#17757](https://github.com/kubestellar/console/issues/17757). Stellar GA is the strategic milestone that moves Console from a dashboard to a production AI operations runtime. |
128 | | -- **GitOps integration milestone** — First-class Flux + Argo CD support with observability parity, declarative Console configuration, and Mission Control deep links; see `docs/plans/GITOPS-INTEGRATION-RFC.md` |
129 | | -- **Multi-tenant RBAC** — Role-based access control for teams sharing a Console instance, with namespace-scoped permissions |
130 | | -- **Plugin architecture** — Extensible card and mission system allowing third-party developers to build custom dashboard components; see `docs/plans/PLUGIN-ARCHITECTURE-RFC.md` (RFC to be authored — tracked in [#17760](https://github.com/kubestellar/console/issues/17760)) |
131 | | -- **Helm operator** — Kubernetes operator for fleet-wide Console deployment and lifecycle management |
132 | | -- **Enhanced AI missions** — AI-assisted troubleshooting missions that diagnose cluster issues and suggest remediation steps |
133 | | -- **Offline/air-gapped mode** — Full Console functionality without internet connectivity for restricted environments |
134 | | -- **CNCF incubation preparation** — Governance documentation, adopters program, and community growth metrics; target Q4 2026 TOC application |
135 | | -- **Third-party security audit (Q3 2026)** — Engage CNCF-sponsored auditors (ADA Logics or CNCF Security Audit program) for formal code security audit; required gate for CNCF incubation. **Owner:** clubanderson. **Timeline:** Open CNCF Security Audit request at https://github.com/cncf/toc/issues in Q2 2026; schedule audit completion for Q3 2026. This positions the project for Q4 2026 incubation application with completed security due-diligence. |
136 | | -- **Multi-model AI backend** — Support for multiple LLM providers (OpenAI, Ollama, vLLM) behind a unified mission interface, reducing vendor lock-in |
137 | | -- **Webhook-driven card updates** — Push-based card refresh via Kubernetes webhooks instead of polling, reducing API server load on large clusters |
138 | | -- **Custom alert rules** — User-defined threshold alerts on any card metric, with notification channels (Slack, email, PagerDuty) |
139 | | - |
140 | | ---- |
141 | | - |
142 | | -## Long-Term (2027+) — Vision & Innovation |
143 | | - |
144 | | -Strategic initiatives for organizational scale, advanced operations, and ecosystem leadership. |
145 | | - |
146 | | -- **Policy engine** — Built-in policy authoring, testing, and enforcement with OPA/Gatekeeper integration |
147 | | -- **AI-assisted operations** — Proactive anomaly detection, capacity planning, and automated incident response via MCP |
148 | | -- **Federation** — Console-to-Console federation for organizations managing multiple Console instances across regions |
149 | | -- **Compliance dashboards** — Automated compliance reporting against CIS benchmarks, SOC 2, and HIPAA requirements |
150 | | -- **Collaborative dashboards** — Real-time multi-user dashboard editing with presence indicators and conflict resolution |
151 | | -- **Workflow automation** — Visual workflow builder for multi-step cluster operations (rolling upgrades, canary deployments, disaster recovery runbooks) |
152 | | -- **Embedded terminal** — In-browser kubectl/helm terminal with context-aware autocomplete, scoped to the user's RBAC permissions |
153 | | - |
154 | | ---- |
155 | | - |
156 | | -## Non-Goals / Out of Scope |
157 | | - |
158 | | -KubeStellar Console intentionally does **not** aim to: |
159 | | - |
160 | | -- **Replace kubectl** — Console is a visual companion, not a CLI replacement. Power users should continue using kubectl, helm, and other CLI tools directly. |
161 | | -- **Be a general-purpose IDE** — While Console includes AI-powered features, it is not a code editor or development environment. |
162 | | -- **Manage non-Kubernetes workloads** — Console focuses exclusively on Kubernetes clusters and cloud-native workloads. Other orchestration platforms (Docker Compose, Nomad, CloudFoundry) are out of scope. |
163 | | -- **Provide its own container runtime** — Console observes and manages existing clusters; it does not provision infrastructure or manage container runtimes. |
164 | | -- **Compete with commercial APM tools** — Console provides operational visibility, not deep application performance monitoring. Use Datadog, New Relic, or Grafana for APM. |
165 | | -- **Support EOL Kubernetes versions** — Console targets only actively supported Kubernetes versions (N-2 policy). |
166 | | -- **Offer enterprise support contracts** — Support is community-driven via GitHub Issues, Slack, and mailing lists; commercial support is outside scope. |
167 | | - |
168 | | ---- |
169 | | - |
170 | | -## How to Influence the Roadmap |
171 | | - |
172 | | -We welcome community input on priorities: |
173 | | - |
174 | | -- **GitHub Issues** — Open an issue on [kubestellar/console](https://github.com/kubestellar/console/issues) with the `enhancement` label |
175 | | -- **Discussions** — Join [#kubestellar-dev on Slack](https://cloud-native.slack.com/channels/kubestellar-dev) |
176 | | -- **Mailing List** — Email [kubestellar-dev@googlegroups.com](mailto:kubestellar-dev@googlegroups.com) |
177 | | - |
178 | | ---- |
179 | | - |
180 | | -## Strategic Health — June 2026 |
181 | | - |
182 | | -> Status snapshot filed by the strategist agent (ACMM L6). Updated when material risks to roadmap delivery are identified. |
183 | | -> **Last updated:** 2026-06-12 |
184 | | -
|
185 | | -### Current Risk Register |
186 | | - |
187 | | -| Risk | Severity | Issue | Status | |
188 | | -|------|----------|-------|--------| |
189 | | -| Merge gate disabled on `main` — no required status checks | 🔴 Critical | #17852 | Open | |
190 | | -| Main branch build cascade — 8+ breaks on 2026-06-12, recovery SLA undefined | 🔴 Critical | #17756, #17969 | Escalating | |
191 | | -| Auth smoke test regression | 🔴 Critical | #17824 | Open | |
192 | | -| DCO sign-off failures on automation PRs — legal compliance risk | 🔴 Critical | #17966 | Open | |
193 | | -| Coverage suite — 415 failures risk v0.3 "91% coverage" claim | 🟠 High | #17856 | Open | |
194 | | -| v0.4 feature velocity at zero — all recent merges are maintenance | 🟠 High | #17968 | Ongoing | |
195 | | -| Scanner PR backlog stalling v0.4 arch refactor | 🟠 High | #17853 | Open | |
196 | | -| Stellar subsystem — no GA milestone or alpha exit criteria | 🟡 Medium | #17757 | Open | |
197 | | -| Plugin architecture RFC exists (Draft) but issue tracker not closed | 🟡 Medium | #17760 | RFC exists | |
198 | | -| Organic contributor drought — <4% human PR ratio | 🟡 Medium | #17967 | Ongoing | |
199 | | -| Adoption metrics (`docs/ADOPTION-METRICS.md`) all TBD | 🟡 Medium | #17965 | Unresolved | |
200 | | -| CNCF incubation tracker on `hold` | 🟡 Medium | #4072 | Blocked | |
201 | | - |
202 | | -### v0.4 Delivery Prerequisites |
203 | | - |
204 | | -Before v0.4 ("AI-Native Observability") can ship on-schedule (Q3 2026), the following blockers must be resolved: |
205 | | - |
206 | | -1. **Merge gate enforcement** (#17852) — Must be enabled first; every other quality improvement depends on a stable merge pipeline. |
207 | | -2. **Build stabilization** (#17756) — Main must stay green for at least 2 weeks before any v0.4 feature work is reliable. |
208 | | -3. **Recovery SLA definition** (#17969) — Define build sheriff role, 4-hour SLA, and circuit breaker for automation agents when main is broken. |
209 | | -4. **Coverage regression triage** (#17856) — Determine whether the 415-failure coverage suite is a build environment artifact or real test regression. |
210 | | -5. **v0.4 feature work kickoff** (#17968) — Designate a feature captain and open at least one implementation PR for llm-d, Drasi, or kagent integration. |
211 | | - |
212 | | -### Adoption Readiness |
213 | | - |
214 | | -| Signal | Target | Current | |
215 | | -|--------|--------|---------| |
216 | | -| Main branch build stability | Green ≥14 consecutive days | ❌ Failing (8+ breaks on 2026-06-12) | |
217 | | -| Coverage suite pass rate | >99% | ❌ 415 failures | |
218 | | -| Human contributor ratio | ≥10% of merged PRs | ❌ <4% (1/30 recent merges) | |
219 | | -| ADOPTERS.md confirmed entries | ≥3 production users | ⚠️ TBD | |
220 | | -| Adoption metrics populated | All fields in `docs/ADOPTION-METRICS.md` | ❌ All TBD (#17965) | |
221 | | -| DCO compliance on automation PRs | 100% of merged PRs signed | ⚠️ Gaps identified (#17966) | |
222 | | -| CNCF incubation application | Filed | ⏸ On hold (#4072) | |
| 1 | +/tmp/roadmap-p19.md |
0 commit comments