Weekly RoadmapRoadmap #3425
Closed
Weekly RoadmapRoadmap
#3425
Replies: 1 comment
-
|
This discussion has been marked as outdated by Weekly Roadmap. A newer discussion is available at Discussion #3469. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Executive Summary
--configflag for alternate config files (multi-environment workflows), extendedksail-clusterGitHub Action with GitOps CI support,validateinput in the action,sourceDirectoryfix inworkload validate, and kustomize patch-file skip during individual validation.workload watch), and #3107 (real cluster profile templates) — still the top feature targets.overridesfix.mirrord-previewGitHub Action for preview environments — growing CI/CD overlap with KSail's composite action territory.KSail Current State
Version: v5.73.3 (March 26, 2026)
What KSail Does Today
KSail is a Go single-binary Kubernetes SDK for local and cloud GitOps development. It embeds kubectl, helm, kind, k3d, vcluster, flux, and argocd as Go libraries. Docker is the only required external dependency.
Key differentiators:
--configflag (new this week) enables alternateksail.yamlfor multi-environment setupsksail workload watchmonitorsk8s/and auto-reconciles on changesksail workload validaterespectssourceDirectoryfrom config (fixed this week)--ttlflag auto-destroys clusters after a configurable duration--profileflag forksail cluster init(Default today; real templates pending)cluster_read,cluster_write,workload_read,workload_write,cipher_write)devantler-tech/ksail/.github/actions/ksail-clusterwith GitOps CI support (extended this week)Recent Development (March 23 – 26, 2026)
Strengths
--configflag unlocks dev/staging/prod config separationOpen Issues
ksail cluster updateworkload watchCompetitor Landscape
Comparison Table
--configflag (new)devspace.yamlprofilesworkload watchskaffold dev--ttlmirrord-previewKey Observations
Tilt (9,559 ⭐, +11 week-over-week): Steady incremental growth. Still active (last commit March 26). The
tree-viewalpha from v0.37.0 (March 4) remains the biggest recent competitive signal — topology/dependency visualization is table-stakes expectation for mature Kubernetes tools. KSail'scluster infois the right extension point.mirrord (5,027 ⭐, +13 week-over-week, +27 over two weeks): Most notable new signal — mirrord launched
mirrord-preview(March 16), a GitHub Action for ephemeral preview environments backed by traffic mirroring. This is adjacent to KSail's ephemeral cluster TTL feature. The tools remain complementary (KSail provisions, mirrord mirrors traffic) but mirrord is building CI/CD surface. A KSail + mirrord companion guide remains the right response: low effort, high signal.DevSpace (~4,931 ⭐): Complementary: KSail owns cluster provisioning + GitOps; DevSpace owns hot-reload inner-loop. The companion guide in KSail docs solidifies this positioning. DevSpace's
devspace.yamlprofiles map conceptually to KSail's new--profileand--configflags; this comparison point will resonate with DevSpace users evaluating KSail.ArgoCD (22,414 ⭐): Still leads Flux (7,984 ⭐) by ~2.8× in stars. KSail bootstraps ArgoCD but doesn't scaffold ApplicationSets or Projects. This remains the highest-impact ArgoCD differentiation gap — see "Later" section.
Skaffold (~15,774 ⭐): Most widely adopted build-push-deploy tool. KSail's composite action + ephemeral clusters complement Skaffold workflows; the
--configflag improves multi-environment parity.Flux (7,984 ⭐): OCI-based GitOps (using GHCR as source) is gaining traction — KSail's
ksail workload pushto OCI already supports this pattern.mirrord-previewshows the market wants preview environment workflows backed by GitOps tooling.Industry Trends
1. Multi-Environment Config as Table Stakes (HIGH relevance — just shipped)
The
--configflag shipped this week, enabling explicitksail.yamlper environment (dev, staging, prod). This is a common ask from teams moving from local dev to shared staging clusters. The next natural step is a docs pattern showing how to structure a multi-environment KSail project.Implication: Document the multi-environment pattern with
--configprominently (a dedicated use-case or guide). Teams evaluating KSail for staging/production workflows will find this immediately valuable.2. GitOps CI/CD as a Growth Vector (HIGH relevance — just shipped)
The
ksail-clusteraction now supports GitOps CI end-to-end with avalidateinput. This extends KSail's CI value proposition beyond ephemeral cluster provisioning. Teams using KSail in CI can now validate manifests before reconcile.Implication: Document the GitOps CI workflow clearly in the use-cases and CI/CD guide. The action is the primary KSail growth driver for non-local use cases.
3. Preview Environments as an Emerging Pattern (MEDIUM relevance)
mirrord's
mirrord-previewaction (March 16) signals that the market wants ephemeral environments tied to PRs and CI. KSail already has--ttlfor ephemeral TTL clusters; combining--ttl+ksail-clusteraction creates a natural KSail-native preview environment pattern.Implication: A guide or use-case showing "PR-based preview clusters with KSail" (leveraging
--ttl+ composite action) would differentiate KSail vs mirrord-preview and expand the CI/CD guide.4. Talos Linux 1.13 Upstream Impact (HIGH relevance — ongoing)
Talos 1.13 stable approaches. The
EnvironmentConfigdocument replaces.machine.env;LifecycleServicereplaces the legacy upgrade API;ImageVerificationConfigadds machine-wide image signature verification. KSail's Talos provisioner and generated config patches may need updates.Implication: Audit and migrate generated Talos patches before 1.13 stable to avoid user-facing breakage.
5. Selective GitOps Reconcile (HIGH relevance — open issue)
ksail workload watchreconciles the fullk8s/tree on any file change. In large repos with multiple Kustomizations (e.g., a platform with infra/, apps/, monitoring/ subtrees), full-tree reconcile latency is the dominant inner-loop friction. No competitor addresses this at the GitOps level. Issue #3106 captures this precisely.Implication: Highest-value unshipped feature for active KSail users. No new dependencies required.
6. AI-Augmented Kubernetes Operations Maturing (HIGH relevance)
MCP adoption continues to accelerate. KSail's 5-tool MCP server (
cluster_read/write,workload_read/write,cipher_write) provides the most comprehensive Kubernetes cluster management surface of any tool via MCP. The quality of tool schemas, error messages, and JSON output structure is what determines agentic task success rates.Implication: Invest in MCP tool quality — structured JSON output, actionable error messages — over adding new tools. A "Using KSail with Claude / Cursor" guide would expand MCP discoverability.
7. VSCode Extension Ecosystem (MEDIUM relevance)
The VSCode extension already integrates with the VS Code Kubernetes Create Cluster wizard. The yauzl vulnerability (#3421) is a blocking CI issue that erodes the extension's release pipeline reliability — it should be resolved quickly via
overridesinpackage.json.Implication: Fix yauzl immediately. Long-term: track
@vscode/vscefor upstream fix to retire the override.Roadmap: Now / Next / Later
🟢 Now — Enhance current features, align with open issues
yauzltooverridesinvsce/package.json; runnpm install; commit updatedpackage-lock.jsonoverridesfix unblocks the pipelineworkload watchk8s/treeksail cluster updatepkg/svc/diff/output visually: before/after diff with impact classification (in-place / reboot-required / recreate-required)pkg/svc/diff/infrastructure already computes diffs; exposing them prevents surprise cluster recreations; acceptance criteria in #3130--configguide--config" showing dev/staging/prodksail.yamlpatterns--configshipped this week; no guide exists yet; DevSpace users evaluating KSail will look for this pattern; directly addresses the multi-environment workflow demandksail-clusteraction +--ttl; reference the GitOps CI extension shipped this week--ttl+ composite action + GitOps CI); positions KSail vs mirrord in the CI/CD use case.machine.envdeprecation audit.machine.envusage; migrate toEnvironmentConfigahead of Talos 1.13 stable🔵 Next — Natural extensions of current capabilities
--profilevalues beyondDefault:Mesh(Cilium + mTLS),Observability(Prometheus + Grafana),ArgoCD(ArgoCD engine + ApplicationSet scaffold)--profileis live but no-op; users who see the flag expect real options; #3107 filed; ArgoCD profile serves the largest unaddressed GitOps segmentcluster create/update/deleteagainst a real Omni endpoint; injectOMNI_SERVICE_ACCOUNT_KEYvia GitHub Actions secrets; gate merge on test passmirrord-previewraising CI/CD profile; growing adoption in same user segment; guide follows established DevSpace/Telepresence patterncluster_read,workload_readoutput for consistent JSON structure; ensure all error messages are actionable and schema-accuratetable/table.goto tablewriter v1.x API; removepatches/loft-sh-log/once merged🟡 Later — Exploratory, worth watching
cluster init --gitops-engine ArgoCD; add reconcile semantics matching the ArgoCD modelLifecycleServicemigrationLifecycleServiceAPI once stable SDK exposure is confirmed--observabilityflag orObservabilityprofile adding Prometheus + Grafana + OTLP alongside CNI/CSI/policy-engineksail cluster infowith a dependency/resource tree view (inspired by Tilt v0.37.0 alphatree-view)cluster infois the right extension pointImageVerificationConfigin KSail's Talos cluster init scaffolding as an optional security hardening stepHow to Control this Workflow
gh aw disable weekly-roadmap --repo devantler-tech/ksail gh aw enable weekly-roadmap --repo devantler-tech/ksail gh aw run weekly-roadmap --repo devantler-tech/ksail gh aw logs weekly-roadmap --repo devantler-tech/ksail📁 Previous Research — March 23, 2026 (Weekly Roadmap #3294)
Executive Summary (Mar 23)
ReadFileSafe,EvalCanonicalPathrefactor,netretryrobustness, and multi-provisioner test coverage.ImageVerificationConfig, newLifecycleServiceupgrade API.Previous Roadmap Outcomes (Mar 23)
.machine.envdeprecation auditPrevious Competitor Table (Mar 23)
tree-viewdevspace.yamlpresets🔬 Research Methodology
Search Queries Used
GitHub Issues
devantler-tech/ksailopen issues (state=OPEN, perPage=50) viagithub-list_issuesGitHub Pull Requests
repo:devantler-tech/ksail is:pr is:merged merged:>=2026-03-12viagithub-search_pull_requestsGitHub Commits
devantler-tech/ksailmain branch, perPage=30 viagithub-list_commitsGitHub Releases
devantler-tech/ksaillatest release viagithub-get_latest_release→ v5.73.3GitHub Discussions
devantler-tech/ksaildiscussions (orderBy=UPDATED_AT, DESC, perPage=50) viagithub-list_discussionsgithub-get_discussionRepository Searches
tilt-dev/tilt— stars: 9,559metalbear-co/mirrord— stars: 5,027argoproj/argo-cd— stars: 22,414fluxcd/flux2— stars: 7,984Tools Used
report_intent— intent trackingview— README.mdbash— JSON parsing of issues, PRs, commitsgithub-list_issues— open issuesgithub-list_discussions— previous roadmap discussionsgithub-get_discussion— discussion Weekly RoadmapRoadmap #3294 full bodygithub-get_latest_release— v5.73.3 confirmed latestgithub-list_commits— recent commit messages (last 30)github-search_pull_requests— recent merged PRs (last 2 weeks)github-search_repositories×4 — star counts: Tilt, mirrord, ArgoCD, Fluxgithub-list_discussion_categories— category ID foragentic-workflowssafeoutputs-create_discussion— publish this discussionBash Commands Executed
python3 -c "import json,sys; ..."— extract commit messages and PR titles from saved tool output filesWeb Fetches
Limitations
github-get_discussiontoolBeta Was this translation helpful? Give feedback.
All reactions