Agentic Planner - February 1, 2026: Prioritized Development Roadmap #2039

2026-02-01T10:09:37Z

botantler[bot]
bot Feb 1, 2026

Executive Summary

KSail has strong momentum with comprehensive roadmap planning (Discussion #2027) and good repository health (Discussion #2034). The project is at a critical juncture where completing in-flight features (LoadBalancer support, GOPROXY fixes) and addressing infrastructure stability will unlock significant user value.

Current State:

✅ Repository Health: Good (0 NPM vulnerabilities, clean codebase)
🚧 In Progress: LoadBalancer support (PR Daily Roadmap Progress - Add LoadBalancer Support (#1714) #2000), GOPROXY fallback (PR Add GOPROXY fallback for Go module proxy failures #2038)
⚠️ Infrastructure: Go proxy network issues being addressed
📋 Open Issues: 2 bugs, comprehensive feature roadmap exists

Key Priority: Focus on stability and completion before expanding to new features.

Priority Matrix

🔴 Critical (Complete This Week)

1. Merge GOPROXY Fallback Fix (PR #2038)

Issue: #2037 - Daily Test Coverage Improver failing due to Go proxy network errors
Status: PR ready for review
Impact: Unblocks CI/CD pipeline, test coverage improvements, daily workflows
Action: Review and merge PR #2038

2. Resolve CI Matrix Aggregation Issue (#2001)

Issue: GitHub Actions reporting matrix job as failed despite all 82 sub-jobs succeeding
Status: Investigated, recommendations provided
Impact: Prevents valid PRs from merging
Options:

Monitor for recurrence (recommended first step)
Implement API-based verification in status job (if recurs)
Report to GitHub Actions support (if recurs 3+ times)

Next Action: Monitor next 5-10 merge queue runs for pattern recurrence

🟡 High Priority (Complete This Month)

3. Complete LoadBalancer Implementation (#1714)

Status: 70% complete (PR #2000 in review)
Remaining Work:

MetalLB installer for Talos × Docker
hcloud-ccm installer for Talos × Hetzner
Integration tests
Documentation

Why Critical: Essential for dev/prod parity, competitive differentiation
Timeline: 1-2 weeks after PR #2000 merge

4. Official Homebrew Cask (#631)

Status: GoReleaser config exists, needs submission
Work Required:

Test cask locally
Run brew audit
Submit PR to homebrew/homebrew-cask
Update documentation

Why Important: Reduces macOS installation friction, increases discoverability
Timeline: 1 week (mostly process)

5. Cluster Update Command (#1734)

Status: Not started
Scope: Implement ksail cluster update for in-place configuration changes
Why Important: Eliminates delete/recreate cycle, preserves state
Timeline: 2-3 weeks
Dependencies: None (ready to implement)

🟢 Medium Priority (Q1 2026)

6. vCluster Distribution Support (#2017)

Status: Research phase
Strategic Value: Unique differentiator, multi-tenancy, lightweight clusters
Timeline: 4-6 weeks
Dependencies: Complete high-priority items first

7. Interactive TUI Mode (#1835)

Status: Not started
Scope: Add --interactive wizard using Bubbletea
Why Important: Lowers barrier to entry for new users
Timeline: 3-4 weeks
Dependencies: None

8. Cluster Backup/Restore (#1836)

Status: Not started
Scope: Velero-inspired snapshot/restore commands
Complexity: High (state serialization, resource ordering)
Timeline: 6-8 weeks
Dependencies: None

🔵 Low Priority (Q2 2026)

9. Omni Provider for Talos (#1970)

Status: Research phase
Scope: Provision Talos clusters in Sidero Omni
Timeline: 6-8 weeks
Dependencies: Omni account, API credentials

10. KSail Hub - Community Recipe Ecosystem

Status: Concept phase (from Discussion #2027)
Scope: Central repository of pre-configured stacks
Timeline: 8-12 weeks
Dependencies: Community engagement strategy

Dependencies & Blockers

Immediate Blockers

✅ PR Add GOPROXY fallback for Go module proxy failures #2038 - Blocks CI/CD pipeline (ready to merge)
⚠️ Issue CI Failure DoctorMatrix job aggregation failure despite all sub-jobs succeeding #2001 - Needs monitoring (not blocking if rare occurrence)

Sequential Dependencies

PR #2038 (GOPROXY) → Unblock CI
    ↓
PR #2000 (LoadBalancer Core) → Enable LoadBalancer support
    ↓
#1714 (LoadBalancer MetalLB + hcloud-ccm) → Complete feature
    ↓
#1734 (Cluster Update) → Lifecycle improvements
    ↓
#2017 (vCluster) → Distribution expansion

Timeline Recommendation

Risk Assessment

Infrastructure Risks

Risk	Likelihood	Impact	Mitigation
Go proxy network failures	Medium	High	PR #2038 adds fallback (ready to merge)
CI matrix aggregation bugs	Low	Medium	Monitor pattern, add API verification if recurs
Agentic workflow failures	Medium	Low	Isolated to automation, doesn't block development

Development Risks

Risk	Likelihood	Impact	Mitigation
LoadBalancer scope creep	Medium	Medium	Clear MVP definition, defer advanced features
vCluster integration complexity	High	Medium	Research phase first, POC before full implementation
Backup/restore data loss	Low	High	Extensive testing, clear documentation of limitations

Metrics & Success Criteria

Completion Metrics (February)

PR Add GOPROXY fallback for Go module proxy failures #2038 merged
PR Daily Roadmap Progress - Add LoadBalancer Support (#1714) #2000 merged
LoadBalancer feature complete ([feature]: Add --load-balancer flag to ksail cluster init|create #1714)
Homebrew Cask submitted ([feature]: Official Homebrew Cask #631)
CI stability >95% (no matrix aggregation failures)

Quality Metrics (Ongoing)

Test coverage: Maintain >70%
Build time: Keep <5 minutes
Documentation: Update for each feature
CI success rate: Target >95%

Adoption Metrics (Q1 Target)

GitHub stars: 150+ (currently 125)
Homebrew installs: Track after cask release
VSCode extension downloads: Monitor trends

Suggested New Issues

The comprehensive roadmap in Discussion #2027 covers most planned work. The following issues would fill gaps:

# Infrastructure stability tracking
gh issue create \
  --repo devantler-tech/ksail \
  --title "Track CI matrix aggregation stability (Feb 2026)" \
  --label "infrastructure,monitoring" \
  --body "## Objective
Monitor GitHub Actions matrix job aggregation behavior over February 2026 to determine if issue #2001 pattern recurs.

## Tracking
- [ ] Week 1 (Feb 1-7): ___ merge_group runs, ___ failures
- [ ] Week 2 (Feb 8-14): ___ merge_group runs, ___ failures
- [ ] Week 3 (Feb 15-21): ___ merge_group runs, ___ failures
- [ ] Week 4 (Feb 22-28): ___ merge_group runs, ___ failures

## Success Criteria
- If 0 recurrences: Close as resolved
- If 1-2 recurrences: Implement API verification in status job
- If 3+ recurrences: Report to GitHub Actions support

## Related
- #2001: Original matrix aggregation failure investigation"

# LoadBalancer MetalLB implementation (if not already tracked)
gh issue create \
  --repo devantler-tech/ksail \
  --title "Add MetalLB installer for Talos × Docker LoadBalancer support" \
  --label "enhancement,loadbalancer" \
  --body "## Context
Part of LoadBalancer support (#1714). PR #2000 adds Cloud Provider KIND for Vanilla × Docker. This issue tracks MetalLB installer for Talos × Docker.

## Implementation
1. Create MetalLB installer in \`pkg/svc/installer/loadbalancer/metallb/\`
2. Add LoadBalancer configuration for Talos provisioner
3. Update LoadBalancer enum to trigger MetalLB installation
4. Add unit tests for MetalLB installer
5. Add integration tests (Talos cluster + LoadBalancer service)
6. Document MetalLB configuration options

## Acceptance Criteria
- [ ] Talos × Docker clusters with LoadBalancer=MetalLB successfully install MetalLB
- [ ] LoadBalancer services receive external IPs
- [ ] Unit tests cover MetalLB installation logic
- [ ] Integration tests verify end-to-end functionality
- [ ] Documentation updated with Talos × MetalLB support

## Dependencies
- Requires PR #2000 merged
- Part of #1714 (LoadBalancer support)

## Timeline
1-2 weeks after PR #2000 merge"

# LoadBalancer hcloud-ccm implementation
gh issue create \
  --repo devantler-tech/ksail \
  --title "Add hcloud-ccm installer for Talos × Hetzner LoadBalancer support" \
  --label "enhancement,loadbalancer,hetzner" \
  --body "## Context
Part of LoadBalancer support (#1714). This issue tracks hcloud Cloud Controller Manager installer for Talos × Hetzner.

## Implementation
1. Create hcloud-ccm installer in \`pkg/svc/installer/loadbalancer/hcloudccm/\`
2. Add LoadBalancer configuration for Talos provisioner on Hetzner
3. Configure API token injection from environment (HCLOUD_TOKEN)
4. Update LoadBalancer enum to trigger hcloud-ccm installation
5. Add unit tests for hcloud-ccm installer
6. Add integration tests (Talos × Hetzner cluster + LoadBalancer service)
7. Document hcloud-ccm configuration and prerequisites

## Acceptance Criteria
- [ ] Talos × Hetzner clusters with LoadBalancer=HCloud successfully install hcloud-ccm
- [ ] LoadBalancer services receive Hetzner Load Balancer IPs
- [ ] HCLOUD_TOKEN authentication working
- [ ] Unit tests cover hcloud-ccm installation logic
- [ ] Integration tests verify cloud load balancer provisioning
- [ ] Documentation includes prerequisites and setup

## Dependencies
- Requires PR #2000 merged
- Part of #1714 (LoadBalancer support)
- Requires Hetzner account and HCLOUD_TOKEN

## Timeline
1-2 weeks after PR #2000 merge"

# Cluster update command implementation
gh issue create \
  --repo devantler-tech/ksail \
  --title "Implement \`ksail cluster update\` command for in-place configuration changes" \
  --label "enhancement,cluster-lifecycle" \
  --body "## User Story
As a KSail user, I want to update my cluster configuration without destroying and recreating it, so I can add/remove components while preserving workloads and data.

## Current Behavior
Users must \`ksail cluster delete && ksail cluster create\` to change configuration, losing all workloads and data.

## Proposed Behavior
\`ksail cluster update\` detects configuration changes and applies them in-place:
- Add/remove CNI (Cilium, Calico)
- Add/remove CSI (enabled/disabled)
- Add/remove metrics-server
- Add/remove cert-manager
- Add/remove policy engines (Kyverno, Gatekeeper)
- Add/remove LoadBalancer support (when #1714 complete)
- Scale control plane/worker nodes

## Implementation Plan
1. Add \`ksail cluster update\` command to CLI
2. Implement config diff detection (compare running cluster vs ksail.yaml)
3. Create component addition/removal orchestration
4. Add \`--dry-run\` flag to preview changes
5. Add confirmation prompt (reuse deletion confirmation pattern)
6. Handle immutable fields with clear error messages
7. Add rollback on failure
8. Unit tests for diff detection and orchestration
9. Integration tests for component updates
10. Documentation with examples

## Acceptance Criteria
- [ ] \`ksail cluster update\` applies configuration changes in-place
- [ ] \`--dry-run\` shows planned changes without applying
- [ ] Confirmation prompt prevents accidental updates
- [ ] Immutable fields (distribution, provider) rejected with clear errors
- [ ] Workloads and data preserved during updates
- [ ] Rollback on partial failure
- [ ] Comprehensive tests and documentation

## Out of Scope (Future Enhancements)
- Kubernetes version upgrades
- Node OS updates
- Network reconfiguration

## Timeline
2-3 weeks

## Related
- Referenced in Discussion #2027 roadmap (Sprint 2)"

# Documentation: LoadBalancer support matrix
gh issue create \
  --repo devantler-tech/ksail \
  --title "Document LoadBalancer support matrix and configuration examples" \
  --label "documentation,loadbalancer" \
  --body "## Context
After LoadBalancer support (#1714) is complete, we need comprehensive documentation.

## Documentation Needs

### 1. Support Matrix Table
Create table showing LoadBalancer support per distribution × provider:

| Distribution | Provider | LoadBalancer Option | Implementation |
|--------------|----------|---------------------|----------------|
| Vanilla | Docker | Default | Cloud Provider KIND |
| K3s | Docker | Default | K3d ServiceLB (disabled if specified) |
| Talos | Docker | MetalLB | MetalLB installer |
| Talos | Hetzner | HCloud | hcloud-ccm installer |

### 2. Configuration Examples
- Default LoadBalancer (per distribution)
- Explicit LoadBalancer selection
- LoadBalancer=Disabled for all distributions
- Service manifests with LoadBalancer type

### 3. Troubleshooting Guide
- LoadBalancer service stuck in Pending
- IP address not assigned
- Cloud provider logs
- Common misconfigurations

### 4. CLI Flags Reference
Auto-generated docs in \`docs/src/content/docs/cli-flags/\` should cover LoadBalancer flag.

## Acceptance Criteria
- [ ] Support matrix table in main documentation
- [ ] Configuration examples for each combination
- [ ] Troubleshooting section
- [ ] CLI flags reference updated
- [ ] README.md mentions LoadBalancer support

## Dependencies
- Requires #1714 (LoadBalancer implementation) complete

## Timeline
1 week after LoadBalancer feature complete"

# Homebrew Cask audit and submission
gh issue create \
  --repo devantler-tech/ksail \
  --title "Audit and submit KSail Homebrew Cask to homebrew-core" \
  --label "distribution,macos" \
  --body "## Objective
Publish KSail to official Homebrew Cask repository for \`brew install --cask ksail\` installation.

## Current State
- ✅ GoReleaser config exists (auto-publishes to devantler-tech/homebrew-tap)
- ⏳ Not yet submitted to homebrew/homebrew-cask

## Implementation Steps

### 1. Local Verification
\`\`\`bash
# Test installation from tap
brew install --cask devantler-tech/tap/ksail

# Run audit
brew audit --cask --new-cask ksail

# Fix any audit warnings
\`\`\`

### 2. Audit Requirements
Ensure cask meets Homebrew standards:
- [ ] Correct app bundle structure
- [ ] Valid SHA256 checksums
- [ ] Proper uninstall configuration
- [ ] No installer scripts (direct extraction preferred)
- [ ] Appropriate zap stanzas for complete removal

### 3. Submission
\`\`\`bash
# Fork homebrew-cask
gh repo fork homebrew/homebrew-cask

# Create cask formula
cd homebrew-cask/Casks/k
# Copy/adapt from devantler-tech/homebrew-tap

# Submit PR
gh pr create --repo homebrew/homebrew-cask --title \"Add KSail cask\" --body \"...\"
\`\`\`

### 4. Review Process
- Address maintainer feedback
- Update formula as needed
- Wait for CI checks to pass
- Merge

### 5. Documentation Update
After merge:
- Update installation docs to prefer official cask
- Document tap as fallback for development versions

## Acceptance Criteria
- [ ] Local audit passes
- [ ] PR submitted to homebrew/homebrew-cask
- [ ] PR merged
- [ ] Users can \`brew install --cask ksail\`
- [ ] Documentation updated

## Timeline
1 week (mostly waiting for review)

## Related
- #631: Original feature request
- Discussion #2027: Roadmap Sprint 2"

Notes

Existing Roadmap Alignment

This plan builds on the comprehensive roadmap in Discussion #2027 with these adjustments:

Elevated GOPROXY fix to critical priority (blocks CI)
Added CI matrix monitoring as explicit tracking item
Preserved Sprint structure from original roadmap
Focused on completion over expansion

Assumptions

PR Add GOPROXY fallback for Go module proxy failures #2038 ready to merge (pending review)
PR Daily Roadmap Progress - Add LoadBalancer Support (#1714) #2000 needs review and completion
Issue CI Failure DoctorMatrix job aggregation failure despite all sub-jobs succeeding #2001 may be rare GitHub Actions platform issue
Existing agentic workflows continue to provide value despite occasional failures

Next Steps for Maintainers

Review and merge PR Add GOPROXY fallback for Go module proxy failures #2038 (unblocks CI)
Monitor Issue CI Failure DoctorMatrix job aggregation failure despite all sub-jobs succeeding #2001 pattern over next 2 weeks
Review PR Daily Roadmap Progress - Add LoadBalancer Support (#1714) #2000 (LoadBalancer core)
Validate suggested new issues before creation
Provide feedback on this plan via comments

How to Respond to This Plan

Add comments to this discussion with:

Priority adjustments
Timeline concerns
Resource constraints
Alternative approaches
Additional context

The next Agentic Planner run will incorporate your feedback.

Generated by: Agentic Planner
Date: February 1, 2026
Repository: devantler-tech/ksail
Workflow Run: [Link](https://github.com/devantler-tech/ksail/actions/runs/${{ github.run_id }})

AI generated by Agentic Planner

expires on Feb 8, 2026, 10:09 AM UTC

2026-02-08T10:47:57Z

github-actions[bot]
bot Feb 8, 2026

This discussion was automatically closed because it expired on 2026-02-08T10:09:36.906Z.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Agentic Planner - February 1, 2026: Prioritized Development Roadmap #2039

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Agentic Planner - February 1, 2026: Prioritized Development Roadmap #2039

Uh oh!

botantler[bot] bot Feb 1, 2026

Executive Summary

Priority Matrix

🔴 Critical (Complete This Week)

1. Merge GOPROXY Fallback Fix (PR #2038)

2. Resolve CI Matrix Aggregation Issue (#2001)

🟡 High Priority (Complete This Month)

3. Complete LoadBalancer Implementation (#1714)

4. Official Homebrew Cask (#631)

5. Cluster Update Command (#1734)

🟢 Medium Priority (Q1 2026)

6. vCluster Distribution Support (#2017)

7. Interactive TUI Mode (#1835)

8. Cluster Backup/Restore (#1836)

🔵 Low Priority (Q2 2026)

9. Omni Provider for Talos (#1970)

10. KSail Hub - Community Recipe Ecosystem

Dependencies & Blockers

Immediate Blockers

Sequential Dependencies

Timeline Recommendation

Week 1-2 (Feb 1-14)

Week 3-4 (Feb 15-28)

Month 2 (March 2026)

Month 3 (April 2026)

Risk Assessment

Infrastructure Risks

Development Risks

Metrics & Success Criteria

Completion Metrics (February)

Quality Metrics (Ongoing)

Adoption Metrics (Q1 Target)

Suggested New Issues

Notes

Existing Roadmap Alignment

Assumptions

Next Steps for Maintainers

How to Respond to This Plan

Replies: 1 comment

Uh oh!

github-actions[bot] bot Feb 8, 2026

botantler[bot]
bot Feb 1, 2026

github-actions[bot]
bot Feb 8, 2026