Daily BuilderResearch, Roadmap and Plan #3030
Replies: 3 comments
-
|
Note The pull request was not created — a fallback review issue was created instead due to protected file changes: #3080 Worked on CI workflow hardening (plan priority #4 from Daily Workflow Maintenance #3022): added
|
Beta Was this translation helpful? Give feedback.
-
|
Worked on dedicated mirrord companion guide (#3108): created
Warning
|
Beta Was this translation helpful? Give feedback.
-
|
Worked on real cluster profile templates (#3107): added
Warning
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Repository Overview
KSail v5.56.0 — A Go single-binary Kubernetes SDK supporting 4 distributions (Vanilla/Kind, K3s/K3d, Talos, VCluster) and 3 providers (Docker, Hetzner, Omni). Embeds kubectl, helm, kind, k3d, vcluster, flux, and argocd as Go libraries. Docker is the only required external dependency.
As of March 13, 2026:
next, 2blocked)ksail workload watch,--ttlephemeral clusters, Flux distribution images in mirror cache warming, three-step cluster stability check, golangci-lint + jscpd Copilot hooks🔴 High-Priority Bugs
None currently — the previous
npm auditvulnerability issue has been resolved. CI is green.🚀 High-Impact Roadmap Features
1. Add MCP Write-Operation Tools —
cluster_update,workload_apply,cipher_encrypt/decrypt(#3029)Source: Issue #3029 (created by Daily Plan today); Weekly Research March 13 "Now" priority
Impact: MCP read-only tools already live; adding write operations unlocks autonomous agentic cluster management — a unique competitive advantage over all competitors. VS Code, JetBrains, and Zed all now have first-class MCP client support.
Approach: Locate current MCP tool registrations in
pkg/svc/mcp/, add handlers forcluster_update,workload_apply,cipher_encrypt,cipher_decrypt. FollowargsKeyconstant convention.Effort: Small–Medium (3–6 hours)
Files:
pkg/svc/mcp/,pkg/toolgen/2. CI Integration Guide for Ephemeral Clusters (
--ttl) (#3027)Source: Issue #3027 (created by Daily Plan today); Weekly Research March 13 "Now" priority
Impact:
--ttlshipped in v5.56.0 but has no adoption-driving documentation. Highest-ROI docs investment given the feature is live. Ephemeral environments are now standard CI practice.Approach: Author
docs/src/content/docs/guides/ci-cd-ephemeral-clusters.mdxwith GitHub Actions pattern usingksail cluster create --ttl 1h, kubeconfig forwarding, cleanup on failure, and minimal end-to-end workflow YAML.Effort: Small (1–2 hours)
Files:
docs/src/content/docs/guides/ci-cd-ephemeral-clusters.mdx,docs/astro.config.mjs(sidebar)3. Selective Kustomization Reconcile in
workload watch(#3028)Source: Issue #3028 (created by Daily Plan today); Weekly Research March 13 "Now" priority
Impact:
workload watchcurrently triggers a fullk8s/reconcile on any file change. In large repos with many Kustomization overlays, this creates unnecessary reconcile cycles. Smarter watch = faster developer feedback.Approach: Map changed file paths to their containing Kustomization directory; trigger
flux reconcile kustomization (name)for only the affected subtree; fall back to full reconcile for ambiguous changes.Effort: Medium (4–6 hours)
Files:
pkg/cli/cmd/workload/watch.go(or the watch lifecycle path),pkg/client/flux/4. Talos × Omni CI System Tests (#2810 / PR #2547)
Source: Issue #2810 (March 5); Weekly Research March 13 "Now" priority; PR #2547 exists but needs rebase
Impact: Only provider with zero CI system test coverage. Enterprise evaluators who hit undiscovered Omni bugs will churn. PR #2547 is code-complete but diverged ~7 commits from main.
Approach: Rebase PR #2547 onto current
main, verify secrets (OMNI_SERVICE_ACCOUNT_KEY,OMNI_ENDPOINT) are configured in the repo, merge.Effort: Small (1–2 hours for rebase)
Files:
.github/workflows/ci.yaml,.github/actions/ksail-system-test/action.yaml🔧 Backlog Improvements
5. Test Coverage —
pkg/cli/cmd/workload/gen/(from Daily Code Quality #3004)Source: Daily Code Quality discussion #3004
Impact: 19 source files in resource generators; only
gen_test.goandhelm_release_test.goexist. All resource generators (namespace, deployment, service, configmap, secret, role, etc.) are entirely untested.Approach: Table-driven tests per generator following the
kyvernopattern:helm.NewMockInterface(t),t.Parallel(),require.NoError.Effort: Medium (3–5 hours)
6. Refactor
pkg/client/kubectl/client.go(682 lines, 46 functions) (from Daily Code Quality #3004)Source: Daily Code Quality discussion #3004
Impact: Largest file with the most functions in
pkg/client/. Clear groupings (CRUD, diagnostic, watch) map directly to 3–4 smaller files. High discoverability and maintainability impact.Effort: Medium (2–4 hours, mostly mechanical)
7. CI Improvements (from Daily Workflow Maintenance #3022)
Source: Daily Workflow Maintenance discussion #3022
Priority sub-items:
pathsfilter totest-pages.yaml— eliminates unnecessary runner minutes on code-only PRsactions/delete-package-versions@v5to SHA inmaintenance.yaml— closes supply-chain security gaptimeout-minutestotest-pages.yamlandpublish-pages.yamlEffort: Small (30 min each)
8. Companion Tool Documentation — DevSpace, Telepresence, mirrord
Source: Weekly Research March 13 (new this week: DevSpace 4,929 ⭐, Telepresence 7,149 ⭐ identified as KSail companions)
Impact: Captures users coming from hot-reload and traffic-mirroring tools. Complements existing KSail inner-loop story.
Effort: Medium (2–3 hours)
🗑️ Stale/Closeable Items
9. Blocked Upstream Items (monitor only)
chore: evaluate filing upstream issue for VCluster D-Bus race— Workaround in place viarecoverFromDBusError. Actionable item: file the upstream loft-sh/vcluster issue to get the debt resolved.chore: remove loft-sh/log fork— Blocked on external upstream PR toloft-sh/log. Monitor only; no code change possible until upstream merges.Priority Order for Implementation
--ttlephemeral clusters (#3027)pkg/cli/cmd/workload/gen/(#3004)pkg/client/kubectl/client.go(#3004)How to Control this Workflow
You can add comments to this discussion to provide feedback or adjustments to the plan. Available commands:
gh aw disable daily-builder --repo devantler-tech/ksail gh aw enable daily-builder --repo devantler-tech/ksail gh aw run daily-builder --repo devantler-tech/ksail --repeat (number-of-repeats) gh aw logs daily-builder --repo devantler-tech/ksailWhat Happens Next
The next time this workflow runs, it will begin implementing items from the plan based on priority:
--ttlephemeral clusters ([chore]: add CI/CD integration guide for ephemeral clusters with --ttl #3027) — small effort, high adoption valueIf running in "repeat" mode, the workflow will automatically run again to continue working on items. Humans can review this research and add comments to adjust priorities before the workflow continues.
Beta Was this translation helpful? Give feedback.
All reactions