Agentic PlannerFebruary 9, 2026: Development Roadmap Status

[botantler[bot]]

Executive Summary

KSail development continues at strong pace with 14 open issues across feature development and infrastructure. The project shows excellent health with a clear focus on LoadBalancer support and cluster lifecycle enhancements for production readiness.

Current State:

• ✅ Repository Health: Excellent - stable CI/CD, current dependencies, comprehensive test coverage
• 🚧 Active Development: LoadBalancer support ([feature]: Add --load-balancer flag to ksail cluster init|create #1714) and cluster update command ([feature]: add ksail cluster update for in-place updating a cluster #1734) as critical priorities
• ⚠️ Infrastructure Issues: Minor workflow issues ([agentics] Update Docs failed #2061, Daily Test Coverage Improver - Go Module Proxy Infrastructure Failure #2079) - external dependencies, non-blocking
• 📋 Test Coverage: Daily Coverage Improver adding comprehensive unit tests (currently blocked by Daily Test Coverage Improver - Go Module Proxy Infrastructure Failure #2079)

Strategic Direction: Deliver production-ready cluster lifecycle features (LoadBalancer, Update, Backup/Restore) before expanding distribution portfolio (vCluster, Omni).

---

Changes Since Previous Plan (Feb 8)

What Changed:

1. Minor Update: Only 1 day elapsed since last plan (Feb 8)
2. Repository Activity: Single commit updating lychee.toml (link checking configuration)
3. Status Confirmation: No new issues, no closures, all priorities remain unchanged

What Stayed the Same:

• ✅ All priorities unchanged from Feb 8 plan
• ✅ LoadBalancer support remains critical priority ([feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069, [feature]: Add Cloud Provider KIND installer for Vanilla × Docker LoadBalancer support #2071, [feature]: Add hcloud-ccm installer for Talos × Hetzner LoadBalancer support #2070, [feature]: Document LoadBalancer support matrix and configuration examples #2074)
• ✅ Cluster update command remains critical priority ([feature]: Implement ksail cluster update core command and config diff detection #2072)
• ✅ CI concurrency fix remains urgent ([feature]: Implement workflow-specific concurrency groups to fix matrix aggregation #2073)
• ✅ Timeline and effort estimates remain accurate
• ✅ Strategic focus: Complete lifecycle features before expanding distributions

Key Insight: The comprehensive plan from February 8 (Discussion #2097) remains accurate and fully applicable. No material adjustments needed.

---

Current Priorities (Unchanged from Feb 8)

🔴 Immediate Action Required

1. CI Concurrency Fix (#2073) ⭐ URGENT - START HERE

Problem: Cross-workflow cancellation causing false CI failures in merge queue

Solution: Make concurrency groups workflow-specific

Implementation:

# Update .github/workflows/ci.yaml
concurrency:
  group: "ci-ksail-${{ github.workflow }}-${{ github.ref }}"
  cancel-in-progress: true

Timeline: 1-2 days
Impact: Closes #1903 as side effect

🔴 Critical Priority: LoadBalancer Support

Week 1-2 (Feb 10-23): Parallel Implementation

Track A: MetalLB for Talos × Docker (#2069) ⭐

• Create pkg/svc/installer/loadbalancer/metallb/ package
• Implement L2 mode configuration
• Add unit and integration tests
• Estimated Effort: 1.5-2 weeks
• Can Start: Immediately (no blockers)

Track B: Cloud Provider KIND for Vanilla × Docker (#2071) ⭐

• Create pkg/svc/installer/loadbalancer/cloudproviderkind/ package
• Implement installer following existing patterns
• Add unit and integration tests
• Estimated Effort: 1.5-2 weeks
• Parallelizable: Yes with [feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069

Week 3-5 (Feb 24 - Mar 19): hcloud-ccm Installer (#2070)
Week 6 (Mar 20-26): LoadBalancer Documentation (#2074)

🔴 Critical Priority: Cluster Update Command

Start Date: After LoadBalancer support complete
Issue: #2072
Timeline: 2-3 weeks

---

Open Issues Inventory (14 Total)

By Priority Category

🔴 Critical (8 issues):

• [feature]: Implement workflow-specific concurrency groups to fix matrix aggregation #2073: CI workflow-specific concurrency (urgent, 1-2 days)
• [feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069: MetalLB installer (high priority, 2 weeks)
• [feature]: Add Cloud Provider KIND installer for Vanilla × Docker LoadBalancer support #2071: Cloud Provider KIND installer (high priority, 2 weeks)
• [feature]: Add hcloud-ccm installer for Talos × Hetzner LoadBalancer support #2070: hcloud-ccm installer (3 weeks)
• [feature]: Document LoadBalancer support matrix and configuration examples #2074: LoadBalancer documentation (1 week)
• [feature]: Implement ksail cluster update core command and config diff detection #2072: Cluster update core command (3 weeks)
• [feature]: add ksail cluster update for in-place updating a cluster #1734: Parent issue for cluster update feature
• CI Failure DoctorRecurring merge_group concurrency race causing false CI failures #1903: CI matrix failure (blocked by [feature]: Implement workflow-specific concurrency groups to fix matrix aggregation #2073)

🟢 Medium (3 issues):

• [feature]: Cluster backup and restore commands (Velero-inspired) #1836: Cluster backup/restore (Q2 2026, 6-8 weeks)
• [feature]: Implement vCluster as a distribution, and use vind for the docker provider #2017: vCluster distribution (Q2 2026, 4-6 weeks)
• [feature]: Add Omni provider for Talos #1970: Omni provider for Talos (Q2 2026, 6-8 weeks)

ℹ️ Infrastructure/Tracking (3 issues):

• [agentic-workflows] Failed runs #2060: Failed runs tracker (auto-managed)
• [agentics] Update Docs failed #2061: Update Docs workflow failure (minor, non-blocking)
• Daily Test Coverage Improver - Go Module Proxy Infrastructure Failure #2079: Go module proxy failure (external issue, blocks coverage improver only)

---

Timeline Overview (Feb-Jun 2026)

February 2026

• Week 1 (Feb 8-14):
  • ⚡ CI concurrency fix ([feature]: Implement workflow-specific concurrency groups to fix matrix aggregation #2073) - URGENT
  • Start MetalLB ([feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069) and Cloud Provider KIND ([feature]: Add Cloud Provider KIND installer for Vanilla × Docker LoadBalancer support #2071) in parallel
• Week 2-3 (Feb 15-28):
  • Complete MetalLB installer
  • Complete Cloud Provider KIND installer

March 2026

• Week 1-3 (Mar 1-19): hcloud-ccm installer ([feature]: Add hcloud-ccm installer for Talos × Hetzner LoadBalancer support #2070)
• Week 3 (Mar 20-26): LoadBalancer documentation ([feature]: Document LoadBalancer support matrix and configuration examples #2074)
• Week 4 (Mar 27 - Apr 2): Start cluster update command ([feature]: Implement ksail cluster update core command and config diff detection #2072)

April 2026

• Week 1-2 (Mar 27 - Apr 9): Complete cluster update core implementation
• Week 3-4 (Apr 10-23): Testing, error handling, rollback for update command

May-June 2026 (Q2)

• Backup/restore ([feature]: Cluster backup and restore commands (Velero-inspired) #1836)
• vCluster support ([feature]: Implement vCluster as a distribution, and use vind for the docker provider #2017) - can run parallel
• Omni provider ([feature]: Add Omni provider for Talos #1970) - can run parallel

---

Success Metrics

February Targets (Week 4 - Feb 28)

• ✅ CI concurrency fix validated (no false failures in 10+ runs)
• ✅ MetalLB installer 80%+ complete
• ✅ Cloud Provider KIND installer 80%+ complete

March Targets (End of Month - Mar 31)

• ✅ All LoadBalancer installers complete and tested
• ✅ LoadBalancer documentation published
• ✅ Cluster update command 50%+ complete

Q1 2026 Targets (End of March)

• ✅ LoadBalancer support released (all installers working)
• ✅ Integration tests passing for all distribution × provider combinations
• ✅ Cluster update command in active development

Q2 2026 Targets (End of June)

• ✅ Cluster update command released
• ✅ At least one of: Backup/Restore, vCluster, or Omni support completed

---

Suggested New Issues to Create

None at this time. All necessary issues exist for current roadmap execution. The plan from February 8 identified all required work items.

Existing Issues Cover All Phases 1-3:

• ✅ [feature]: Implement workflow-specific concurrency groups to fix matrix aggregation #2073: CI workflow-specific concurrency (urgent)
• ✅ [feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069: MetalLB installer (critical)
• ✅ [feature]: Add Cloud Provider KIND installer for Vanilla × Docker LoadBalancer support #2071: Cloud Provider KIND installer (critical)
• ✅ [feature]: Add hcloud-ccm installer for Talos × Hetzner LoadBalancer support #2070: hcloud-ccm installer (critical)
• ✅ [feature]: Document LoadBalancer support matrix and configuration examples #2074: LoadBalancer documentation (critical)
• ✅ [feature]: Implement ksail cluster update core command and config diff detection #2072: Cluster update implementation (critical)
• ✅ [feature]: Cluster backup and restore commands (Velero-inspired) #1836: Backup/restore (medium priority, Q2)
• ✅ [feature]: Implement vCluster as a distribution, and use vind for the docker provider #2017: vCluster distribution (medium priority, Q2)
• ✅ [feature]: Add Omni provider for Talos #1970: Omni provider (medium priority, Q2)

Future Issue Suggestions: When ready to implement Phase 4 work (Backup/Restore, vCluster, Omni), refer to the detailed gh commands in Discussion #2097 for creating implementation sub-issues.

---

Notes for Maintainers

Immediate Actions (Week of Feb 9)

1. 🚨 URGENT: Implement CI concurrency fix ([feature]: Implement workflow-specific concurrency groups to fix matrix aggregation #2073) ⭐ START HERE

   • Why Critical: False CI failures block merge queue, slow down all development
   • Quick Win: 1-2 day effort, high impact
   • Action: Update .github/workflows/ci.yaml and other workflows
   • Validation: Monitor 5-10 merge queue runs

2. Start LoadBalancer Installers in Parallel:

   • Assign [feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069 (MetalLB) to developer/team 1
   • Assign [feature]: Add Cloud Provider KIND installer for Vanilla × Docker LoadBalancer support #2071 (Cloud Provider KIND) to developer/team 2
   • Both can proceed independently, no blockers

Parallelization Opportunities

Phase 2 (Feb 10-23):

• MetalLB ([feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069) and Cloud Provider KIND ([feature]: Add Cloud Provider KIND installer for Vanilla × Docker LoadBalancer support #2071) run simultaneously
• Different distributions, different installers, no conflicts

Phase 4 (Q2 2026):

• Backup/Restore ([feature]: Cluster backup and restore commands (Velero-inspired) #1836), vCluster ([feature]: Implement vCluster as a distribution, and use vind for the docker provider #2017), and Omni ([feature]: Add Omni provider for Talos #1970) are independent
• Can be assigned to different developers/teams

External Dependencies

• Hetzner Cloud Account: Required for [feature]: Add hcloud-ccm installer for Talos × Hetzner LoadBalancer support #2070 testing
• Omni Account: Required for [feature]: Add Omni provider for Talos #1970 (Q2 work)
• Google Go Proxy: Daily Test Coverage Improver - Go Module Proxy Infrastructure Failure #2079 blocked by external infrastructure (non-blocking for main work)

---

Reference Documentation

Comprehensive Plan: For detailed implementation tasks, testing strategies, risk assessment, and technical architecture diagrams, see Discussion #2097 (Feb 8, 2026).

This Plan: Status update confirming roadmap remains on track with no material changes needed.

---

Generated by: Agentic Planner
Date: February 9, 2026
Repository: devantler-tech/ksail
Previous Plan: Discussion #2097 (Feb 8, 2026)
Change Summary: Status confirmation - roadmap unchanged, no new issues, development on track

---

AI generated by Agentic Planner
AI generated by Agentic Planner

AI generated by Agentic Planner

• expires on Feb 16, 2026, 10:26 AM UTC