docs(roadmap): update horizons and add changelog - #226
Conversation
- Move CLI, Headlamp plugin, and cross-resource expressions to Now - Add metrics exporter to Next - Remove API versioning (no committed timeline yet) - Remove packaging (shipped, issue #43 closed Aug 2026) - Add Changelog section; seed with Helm/CRD upgrade hook entry Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Alon Lavian <alavian@nvidia.com>
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughThe roadmap now prioritizes visibility tooling, tested workload coverage, and a Prometheus-compatible metrics exporter. It removes outdated ecosystem tooling entries and records the shipped Helm chart and CRD upgrade hook milestone. ChangesRoadmap updates
Estimated code review effort: 1 (Trivial) | ~3 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
ROADMAP.md (1)
66-89: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winLink each new roadmap item to its tracking issue.
The document defines
Nowwork as tracked by open issues. The newCLI,Headlamp plugin, andMetrics exporterentries do not identify tracking issues. Add the corresponding links, or create the issues before presenting these as active roadmap commitments.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@ROADMAP.md` around lines 66 - 89, Update the roadmap entries for CLI, Headlamp plugin, and Metrics exporter to include links to their corresponding tracking issues, creating those issues first if they do not exist. Keep the existing item descriptions and formatting intact while ensuring each active commitment is traceable to an issue.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@ROADMAP.md`:
- Line 42: Normalize the newly added Markdown in ROADMAP.md, including the
referenced ranges, by removing bold markers from themes and item labels,
replacing any em dash with an ASCII separator, and keeping the text plain ASCII
with short sentences.
---
Nitpick comments:
In `@ROADMAP.md`:
- Around line 66-89: Update the roadmap entries for CLI, Headlamp plugin, and
Metrics exporter to include links to their corresponding tracking issues,
creating those issues first if they do not exist. Keep the existing item
descriptions and formatting intact while ensuring each active commitment is
traceable to an issue.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| Karta workload tree, component status, and pod attribution in a browser-based | ||
| cluster UI without a bespoke dashboard. |
There was a problem hiding this comment.
in a browser-based cluster UI without a bespoke dashboard.
I didn't understand the meaning of this sentence, specifically the term bespoke dashboard.
|
Reworded to: 'Browser-based workload visibility built on the CNCF Headlamp project: shows the Karta workload tree, component status, and pod attribution.' — cleaner and no jargon. |
Summary
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit