Agentic Planner - February 8, 2026: Development Roadmap #2097

2026-02-08T10:10:02Z

botantler[bot]
bot Feb 8, 2026

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).

Activity Analysis (Feb 7-8, 2026)

Recent Activity

Test Coverage Work:

🚀 PR Daily Test Coverage Improver - Labels Package Complete Coverage #2096: Daily Test Coverage Improver - Labels package now has complete coverage (was 0%)
The daily coverage improver continues enhancing test coverage systematically

No Major Changes:

Repository state stable since February 7 plan
No new issues created
No issues resolved
Focus continues on established roadmap priorities

Infrastructure Status

Known Issues (non-blocking):

⚠️ Daily Test Coverage Improver - Go Module Proxy Infrastructure Failure #2079: Go module proxy infrastructure failure (external Google Cloud issue, blocks coverage improver only)
⚠️ [agentics] Update Docs failed #2061: Update Docs workflow failure (minor automation issue)

CI/CD Health:

✅ System tests running successfully
✅ Build pipeline stable
✅ Merge queue operational

Open Issues Inventory (14 Total)

🔴 Critical Priority: LoadBalancer Support (6 issues)

Parent Feature:

[feature]: Add --load-balancer flag to ksail cluster init|create #1714: LoadBalancer support across all distribution × provider combinations

Implementation Tasks (can be parallelized):
2. #2069: Add MetalLB installer for Talos × Docker ⭐ HIGH PRIORITY

Required for: Talos clusters to support LoadBalancer services
Estimated effort: 1.5-2 weeks
Assignable: Yes, can start immediately

[feature]: Add Cloud Provider KIND installer for Vanilla × Docker LoadBalancer support #2071: Add Cloud Provider KIND installer for Vanilla × Docker ⭐ HIGH PRIORITY
- Required for: Vanilla/Kind clusters to support LoadBalancer services
- Estimated effort: 1.5-2 weeks
- Assignable: Yes, can run parallel with [feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069
[feature]: Add hcloud-ccm installer for Talos × Hetzner LoadBalancer support #2070: Add hcloud-ccm installer for Talos × Hetzner
- Required for: Cloud-based Talos clusters to use Hetzner Load Balancers
- Estimated effort: 2-3 weeks
- Dependencies: Requires Hetzner account for testing
- Assignable: Yes
[feature]: Document LoadBalancer support matrix and configuration examples #2074: Document LoadBalancer support matrix and configuration
- Required for: User-facing documentation of LoadBalancer feature
- Dependencies: Requires [feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069, [feature]: Add hcloud-ccm installer for Talos × Hetzner LoadBalancer support #2070, [feature]: Add Cloud Provider KIND installer for Vanilla × Docker LoadBalancer support #2071 complete
- Estimated effort: 4-5 days
- Assignable: Yes

Related Infrastructure:
6. #2073: Implement workflow-specific concurrency groups ⭐ URGENT

Fixes: CI Failure DoctorRecurring merge_group concurrency race causing false CI failures #1903 CI matrix aggregation failures
Impact: Prevents false CI failures blocking merges
Estimated effort: 1-2 days
Assignable: Yes, quick win

🔴 Critical Priority: Cluster Update Command (2 issues)

Parent Feature:
7. #1734: Add ksail cluster update for in-place cluster updates

Implementation Task:
8. #2072: Implement ksail cluster update core command and config diff detection

Enables: In-place configuration changes without cluster recreation
Estimated effort: 2-3 weeks
Dependencies: LoadBalancer support should be complete first (testing scenarios)
Assignable: Yes

🟡 High Priority: CI Stability (1 issue)

CI Failure DoctorRecurring merge_group concurrency race causing false CI failures #1903: CI Failure - Recurring merge_group concurrency race
- Blocked by: [feature]: Implement workflow-specific concurrency groups to fix matrix aggregation #2073 (concurrency fix)
- Will close automatically once [feature]: Implement workflow-specific concurrency groups to fix matrix aggregation #2073 is implemented and validated

🟢 Medium Priority: Future Features (3 issues)

[feature]: Cluster backup and restore commands (Velero-inspired) #1836: Cluster backup and restore commands (Velero-inspired)
- Timeline: Q2 2026 (April-June)
- Estimated effort: 6-8 weeks
- Dependencies: Best started after Update command complete
[feature]: Implement vCluster as a distribution, and use vind for the docker provider #2017: Implement vCluster as a distribution
- Timeline: Q2 2026 (April-June)
- Estimated effort: 4-6 weeks
- Can run parallel with other Q2 work
[feature]: Add Omni provider for Talos #1970: Add Omni provider for Talos
- Timeline: Q2 2026 (April-June)
- Estimated effort: 6-8 weeks
- Requires: Omni account for testing

ℹ️ Infrastructure/Tracking (2 issues)

[agentic-workflows] Failed runs #2060: Failed runs tracker (parent issue for agentic workflow failures)
- Purpose: Organizational tracking, auto-managed
[agentics] Update Docs failed #2061: Update Docs workflow failure
- Impact: Minor, non-blocking
- Can be debugged opportunistically

⚠️ Blocked/External (1 issue)

Daily Test Coverage Improver - Go Module Proxy Infrastructure Failure #2079: Daily Test Coverage Improver - Go Module Proxy failure
- Root cause: External Google Cloud infrastructure issue
- Impact: Blocks coverage improver only, does not affect main development
- Resolution: Wait for Google infrastructure recovery

Priority Roadmap (Feb-June 2026)

Phase 1: Infrastructure Stability (Week of Feb 8-14)

Immediate Action Required:

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

Tasks:

Update .github/workflows/ci.yaml concurrency configuration
Apply same pattern to other workflows (ci-go, etc.)
Test with merge queue runs
Monitor 5-10 runs to validate fix
Document pattern in workflow best practices

Timeline: 1-2 days
Success Criteria: Zero false failures from concurrency races
Impact: Closes #1903 as side effect

Phase 2: LoadBalancer Support (Feb 10 - Mar 26, ~6 weeks)

Goal: Enable LoadBalancer services across all distribution × provider combinations

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

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

Why This Matters: Talos is gaining traction; LoadBalancer support is essential for production use cases

Tasks:

Create pkg/svc/installer/loadbalancer/metallb/ package
Implement MetalLB installer following existing installer patterns
- Reference: pkg/svc/installer/cni/ packages for pattern
- Reference: pkg/svc/installer/metrics/ for Helm-based installer pattern
Configure L2 mode by default for local Docker environments
Add unit tests with mock Kubernetes client
Add integration test: Talos cluster + LoadBalancer service
Document MetalLB setup and troubleshooting

Estimated Effort: 1.5-2 weeks
Assignable: Yes
Can Start: Immediately (no blockers)

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

Why This Matters: Vanilla/Kind is the most popular local development option; LoadBalancer support rounds out the feature set

Tasks:

Create pkg/svc/installer/loadbalancer/cloudproviderkind/ package
Implement Cloud Provider KIND installer
- Reference: KIND documentation for cloud-provider-kind setup
- Use Helm or direct manifest installation
Add unit tests for installation logic
Add integration test: Vanilla cluster + LoadBalancer service
Document Cloud Provider KIND setup

Estimated Effort: 1.5-2 weeks
Assignable: Yes
Can Start: Immediately (no blockers)
Parallelizable: Yes with #2069

Week 3-5 (Feb 24 - Mar 19): Hetzner Cloud Support

hcloud-ccm Installer (#2070)

Why This Matters: Enables production cloud deployments with Talos on Hetzner

Tasks:

Create pkg/svc/installer/loadbalancer/hcloudccm/ package
Implement hcloud-cloud-controller-manager installer
Configure HCLOUD_TOKEN authentication injection
Add unit tests for installation logic
Add integration test: Talos × Hetzner + LoadBalancer service
Document prerequisites, token setup, and troubleshooting

Prerequisites: Hetzner account for testing
Estimated Effort: 2-3 weeks
Assignable: Yes

Week 6 (Mar 20-26): Documentation & Polish

LoadBalancer Documentation (#2074)

Tasks:

Create support matrix table (Distribution × Provider × LoadBalancer)
Write configuration examples for each combination
Create troubleshooting guide:
- Service stuck in Pending state
- IP address not assigned
- Cloud provider logs analysis
- Common misconfigurations
Update CLI flags reference (auto-generated)
Update README with LoadBalancer support mention

Estimated Effort: 4-5 days
Assignable: Yes
Dependencies: All installers complete

Phase 2 Success Criteria:

✅ LoadBalancer services work on Vanilla × Docker (Cloud Provider KIND)
✅ LoadBalancer services work on K3s × Docker (ServiceLB - already working)
✅ LoadBalancer services work on Talos × Docker (MetalLB)
✅ LoadBalancer services work on Talos × Hetzner (hcloud-ccm)
✅ Comprehensive documentation with troubleshooting guides
✅ Integration tests passing for all combinations
✅ Support matrix clearly documented

Phase 3: Cluster Update Command (Mar 20 - Apr 16, ~4 weeks)

Goal: Enable in-place cluster configuration updates without recreation

Why This Matters: Major UX improvement - avoid destroying clusters for config changes

Week 1-2 (Mar 20 - Apr 2): Core Implementation

Core Update Implementation (#2072)

Tasks:

Add ksail cluster update command to CLI
- Location: pkg/cli/cmd/cluster/update.go
- Pattern: Similar to cluster create flow
Implement config diff detection
- Compare running cluster state vs ksail.yaml
- Detect component additions/removals
- Identify immutable fields
Component addition/removal orchestration
- CNI changes (if supported)
- CSI, metrics-server, cert-manager toggles
- Policy engine changes
- GitOps engine changes
Add --dry-run flag to preview changes
Implement confirmation prompt (reuse deletion confirmation pattern)
Unit tests for diff detection logic

Estimated Effort: 2 weeks

Week 3-4 (Apr 3-16): Error Handling & Testing

Tasks:

Handle immutable fields with clear error messages
- Examples: Distribution, Provider, node counts (may require recreate)
Implement rollback on partial failure
Integration tests for update scenarios:
- Add component to running cluster
- Remove component from running cluster
- Attempt immutable change (should error)
- Dry-run validation
Documentation with examples for common scenarios

Estimated Effort: 2 weeks

Phase 3 Success Criteria:

✅ ksail cluster update applies mutable config changes in-place
✅ --dry-run shows planned changes without applying
✅ Confirmation prompt prevents accidental updates
✅ Immutable changes rejected with clear error messages
✅ Workloads preserved during updates
✅ Rollback works on failures
✅ Comprehensive test coverage
✅ Documentation includes common use cases

Phase 4: Future Features (Q2 2026 - Apr-Jun)

Medium Priority (start after Phase 3 complete)

Cluster Backup/Restore (#1836)

Timeline: 6-8 weeks (Mid-April to early June)

Scope:

ksail cluster backup command (resources + PV data to .tar.gz)
ksail cluster restore command with resource ordering
Metadata tracking (version, timestamp, cluster info)
File system backup approach (v1)

Limitations (v1):

No secret encryption (use SOPS separately)
No cloud provider volume snapshots
No Hetzner block storage snapshots

Dependencies: Phase 3 complete (enables testing backup/restore workflows)

vCluster Distribution (#2017)

Timeline: 4-6 weeks (can run parallel with Backup/Restore)

Scope:

Add vCluster as distribution option
vind integration for Docker provider
Virtual cluster provisioner implementation
Multi-tenancy use cases

Strategic Value: Unique differentiator (lightweight virtual clusters)

Omni Provider for Talos (#1970)

Timeline: 6-8 weeks (can run parallel)

Scope:

Omni client SDK integration
Production cluster management via Omni UI/API
API authentication setup

Prerequisites: Omni account for testing

Critical Path & Dependencies

graph TD
    A[CI Concurrency `Fix #2073`] -->|Stabilizes CI| B[LoadBalancer Phase]
    B -->|Track A| C[MetalLB #2069]
    B -->|Track B| D[Cloud Provider KIND #2071]
    C --> E[LoadBalancer Features Complete]
    D --> E
    E -->|Sequential| F[hcloud-ccm #2070]
    F --> G[LoadBalancer Docs #2074]
    G --> H[Phase 2 Complete]
    
    H -->|Sequential| I[Cluster Update #2072]
    I --> J[Phase 3 Complete]
    
    J -->|Enables| K[Backup/Restore #1836]
    J -->|Independent| L[vCluster #2017]
    J -->|Independent| M[Omni #1970]
    
    A -->|Fixes| N[#1903 CI Matrix Issue]
    
    style A fill:#ffd93d,stroke:#ffa94d
    style C fill:#ff6b6b,stroke:#c92a2a
    style D fill:#ff6b6b,stroke:#c92a2a
    style F fill:#ff6b6b,stroke:#c92a2a
    style I fill:#ff6b6b,stroke:#c92a2a
    style K fill:#6bcf7f,stroke:#37b24d
    style L fill:#6bcf7f,stroke:#37b24d
    style M fill:#6bcf7f,stroke:#37b24d
    style N fill:#ffd93d,stroke:#ffa94d

Critical Path: CI Fix → LoadBalancer (MetalLB + Cloud Provider KIND in parallel) → hcloud-ccm → Documentation → Cluster Update → {Backup/Restore OR vCluster OR Omni in parallel}

Recommended Timeline (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)
- 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

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

Risk Assessment

Risk	Likelihood	Impact	Mitigation
LoadBalancer scope creep	Medium	Medium	Strict MVP: basic L4 LoadBalancer only, defer advanced IPAM/BGP modes
hcloud-ccm testing costs	Low	Low	Use Hetzner free tier credits, coordinate with community for testing
Update command breaks clusters	Medium	High	Extensive dry-run testing, rollback capability, conservative immutability checks
CI concurrency issue persists after fix	Low	Medium	Monitor 10+ merge queue runs, escalate to GitHub support if needed
Go proxy infrastructure (#2079)	High	Low	External Google issue, wait for recovery, non-blocking for main work
MetalLB/KIND integration complexity	Medium	Medium	POC first, leverage existing installer patterns, community support
Backup/restore data loss risk	Low	High	Extensive testing with real data, clear v1 limitations documentation
vCluster integration unexpected complexity	High	Medium	Research/POC phase first, fallback to "future work" if too complex

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

Quality Metrics (Ongoing)

Test Coverage: Maintain >70% (currently trending up with daily improver)
Build Time: Keep <5 minutes
CI Success Rate: Target >95%
Documentation: Every feature has usage guide + examples

Changes Since Previous Plan (Feb 7)

What Changed:

Test Coverage Progress: PR Daily Test Coverage Improver - Labels Package Complete Coverage #2096 adds labels package coverage (was 0%, now complete)
Date Update: Plan date updated to February 8, 2026
Minor Status Confirmation: No new issues, no closures, repository stable

What Stayed the Same:

All priorities remain unchanged
LoadBalancer support remains critical priority
Cluster update command remains critical priority
CI concurrency fix remains urgent
Timeline and effort estimates remain accurate
Strategic focus: Complete lifecycle features before expanding distributions

Key Insight: Plan from February 7 remains accurate and on track. No adjustments needed beyond date update and noting test coverage progress.

Suggested New Issues to Create

None at this time. All necessary issues exist for current roadmap execution:

Existing Issues Cover All Work:

✅ [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, future)
✅ [feature]: Implement vCluster as a distribution, and use vind for the docker provider #2017: vCluster distribution (medium priority, future)
✅ [feature]: Add Omni provider for Talos #1970: Omni provider (medium priority, future)

These issues provide sufficient granularity for Phases 1-3. Additional sub-issues can be created when starting Phase 4 work (Backup/Restore, vCluster, Omni).

Future Issue Suggestions (create when Phase 4 starts):

When ready to implement Backup/Restore (#1836), consider breaking into sub-issues:

# Backup Command Implementation
gh issue create \
  --title "[feature]: Implement ksail cluster backup core functionality" \
  --body "**Parent Issue**: #1836

## Scope
Implement core backup functionality for Kubernetes resources and persistent volume data.

## Tasks
- [ ] Create backup archive structure (.tar.gz)
- [ ] Implement resource export (YAML organized by namespace)
- [ ] Implement PV data backup (file system copy)
- [ ] Add backup metadata file (version, timestamp, cluster info)
- [ ] Unit tests for backup logic
- [ ] Integration tests for backup scenarios

## Acceptance Criteria
- \`ksail cluster backup\` creates valid backup archives
- Resources backed up in correct order (CRDs → Namespaces → Storage → Workloads)
- PV data included when \`--include-volumes=true\`
- Metadata file includes all required fields

**Timeline**: 3-4 weeks" \
  --label "go" \
  --label "next"

# Restore Command Implementation
gh issue create \
  --title "[feature]: Implement ksail cluster restore core functionality" \
  --body "**Parent Issue**: #1836

## Scope
Implement core restore functionality to apply backup archives to target clusters.

## Tasks
- [ ] Parse backup archive structure
- [ ] Implement resource restore with ordering (CRDs → Namespaces → PVs → PVCs → Workloads)
- [ ] Implement PV data restore
- [ ] Add \`--existing-resource-policy\` flag (none, update)
- [ ] Add restore labels for traceability (ksail.io/backup-name, ksail.io/restore-name)
- [ ] Unit tests for restore logic
- [ ] Integration tests for restore scenarios

## Acceptance Criteria
- \`ksail cluster restore\` applies backup archives successfully
- Resources restored in correct order
- PV data restored to new PVCs
- Existing resources handled per policy flag
- Restore labels applied for traceability

**Timeline**: 3-4 weeks" \
  --label "go" \
  --label "next"

When ready to implement vCluster (#2017), consider breaking into sub-issues:

# vCluster Distribution Provisioner
gh issue create \
  --title "[feature]: Implement vCluster distribution provisioner" \
  --body "**Parent Issue**: #2017

## Scope
Add vCluster as a distribution option in KSail with vind for Docker provider.

## Tasks
- [ ] Research vCluster SDK/API integration patterns
- [ ] Create vCluster provisioner in \`pkg/svc/provisioner/cluster/vcluster/\`
- [ ] Integrate vind for Docker provider support
- [ ] Add \`vCluster\` distribution enum value in \`pkg/apis/cluster/v1alpha1/enums.go\`
- [ ] Update CLI to support vCluster distribution
- [ ] Unit tests for provisioner logic
- [ ] Integration tests for vCluster creation/deletion
- [ ] Documentation for vCluster use cases (multi-tenancy, testing)

## Acceptance Criteria
- \`ksail cluster create --distribution vCluster --provider Docker\` works
- Virtual clusters run inside host cluster
- Multi-tenancy use cases supported
- Lightweight and fast cluster creation

**Timeline**: 4-6 weeks" \
  --label "go" \
  --label "next"

Notes for Maintainers

Immediate Actions (Week of Feb 8)

🚨 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
- Side Effect: Closes #1903 automatically
Start LoadBalancer Installers in Parallel:
- Track A: Assign [feature]: Add MetalLB installer for Talos × Docker LoadBalancer support #2069 (MetalLB) to developer/team 1
- Track B: 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
Monitor Infrastructure Issues:
- Daily Test Coverage Improver - Go Module Proxy Infrastructure Failure #2079: Track for Google Go proxy recovery (external, non-blocking)
- [agentics] Update Docs failed #2061: Debug Update Docs workflow opportunistically (minor)

Parallelization Opportunities

Phase 2 Parallelization (Week 1-2):

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) can run simultaneously
Different distributions, different installers, no conflicts

Phase 4 Parallelization (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 hcloud-ccm testing
Omni Account: Required for [feature]: Add Omni provider for Talos #1970 (future work)
Google Go Proxy: Daily Test Coverage Improver - Go Module Proxy Infrastructure Failure #2079 blocked by external infrastructure (non-blocking for main work)

Testing Strategy

LoadBalancer Phase:

Each installer gets dedicated integration test before documentation phase
Test matrix: Distribution × Provider × LoadBalancer type
Validate external IP assignment and service connectivity

Update Command:

Extensive dry-run mode testing to prevent cluster breakage
Test rollback scenarios thoroughly
Test immutable field rejection

Backup/Restore (future):

Test with real workload data and persistent volumes
Document v1 limitations clearly (no encryption, no cloud snapshots)
Verify restore on fresh clusters

Alignment with Project Vision

This roadmap aligns with KSail's core mission:

One Binary, Zero Tool Sprawl: LoadBalancer support eliminates need for separate MetalLB/cloud-provider installations
Simple Clusters: Update command enables iterative cluster configuration without recreation
Everything as Code: Backup/restore reinforces declarative cluster management
Production Ready: LoadBalancer + Update + Backup/Restore = production-grade cluster lifecycle management

Strategic Focus: Complete production readiness features (Phases 1-3) before expanding distribution portfolio (Phase 4). This ensures KSail is robust for existing distributions before adding new ones.

Generated by: Agentic Planner
Date: February 8, 2026
Repository: devantler-tech/ksail
Previous Plan: Discussion #2093 (Feb 7, 2026)
Change Summary: Status update, no material changes to roadmap

AI generated by Agentic Planner

AI generated by Agentic Planner

expires on Feb 15, 2026, 10:10 AM UTC

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Agentic Planner - February 8, 2026: Development Roadmap #2097

Uh oh!

{{title}}

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Uh oh!

Agentic Planner - February 8, 2026: Development Roadmap #2097

Uh oh!

botantler[bot] bot Feb 8, 2026

Executive Summary

Activity Analysis (Feb 7-8, 2026)

Recent Activity

Infrastructure Status

Open Issues Inventory (14 Total)

🔴 Critical Priority: LoadBalancer Support (6 issues)

🔴 Critical Priority: Cluster Update Command (2 issues)

🟡 High Priority: CI Stability (1 issue)

🟢 Medium Priority: Future Features (3 issues)

ℹ️ Infrastructure/Tracking (2 issues)

⚠️ Blocked/External (1 issue)

Priority Roadmap (Feb-June 2026)

Phase 1: Infrastructure Stability (Week of Feb 8-14)

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

Phase 2: LoadBalancer Support (Feb 10 - Mar 26, ~6 weeks)

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

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

hcloud-ccm Installer (#2070)

LoadBalancer Documentation (#2074)

Phase 3: Cluster Update Command (Mar 20 - Apr 16, ~4 weeks)

Core Update Implementation (#2072)

Phase 4: Future Features (Q2 2026 - Apr-Jun)

Cluster Backup/Restore (#1836)

vCluster Distribution (#2017)

Omni Provider for Talos (#1970)

Critical Path & Dependencies

Recommended Timeline (Feb-Jun 2026)

February 2026

March 2026

April 2026

May-June 2026

Risk Assessment

Success Metrics

February Targets (Week 4 - Feb 28)

March Targets (End of Month - Mar 31)

Q1 2026 Targets (End of March)

Q2 2026 Targets (End of June)

Quality Metrics (Ongoing)

Changes Since Previous Plan (Feb 7)

Suggested New Issues to Create

Notes for Maintainers

Immediate Actions (Week of Feb 8)

Parallelization Opportunities

External Dependencies

Testing Strategy

Alignment with Project Vision

Replies: 0 comments

botantler[bot]
bot Feb 8, 2026