Every change is reviewable
Output is sorted, deterministic and split into one file per resource, so a pull request diff is the change the cluster receives.
How it fits
Helm, Git, HTTPsync→myks
myksrender→rendered/
rendered/commit + review→Argo CD / Flux
Argo CD / Fluxdeploy→clusters
Reviewable manifests for every cluster
GitOps for Kubernetes fleetsMyks takes upstream Helm charts, Git repositories and plain YAML, applies your per-cluster configuration, and writes plain Kubernetes manifests to
rendered/. You commit that output, so every pull request shows what changes in which cluster.brew install --cask mykso/tap/myksnix profile install github:mykso/myksyay -S myks-bindocker pull ghcr.io/mykso/myks:latestFeatures
Define once, override where needed
Environments form a directory tree that inherits from its parents, and applications are instances of reusable prototypes.
Patch charts without forking
ytt overlays modify the rendered output of a chart for one application, one prototype, or every application of an environment.
Fast on large fleets
Smart Mode renders only the applications your changes affect, and applications render in parallel.
Argo CD built in
Generates an Application per application, plus an AppProject and a cluster Secret per environment.
Know where each value comes from
myks inspect apps --provenance names the file that sets every final value; --redundant reports overrides that change nothing.
Components
myks render- Download sources and render manifests for environments and applications.
myks init- Create a new project.
myks inspect- Show environments, applications and prototypes, and where their values come from.
myks cleanup- Remove obsolete rendered manifests and cache entries.
myks migrate- Seed a KCL configuration tree from the ytt data-values files.