v0.12.0
Feature 2.2: cluster GitOps lifecycle (butlerctl)
butlerctl can now manage a tenant cluster's GitOps lifecycle end to end, closing the largest CLI/console capability gap (Feature #4 in the gap audit):
butlerctl cluster gitops <verb> NAME -n <namespace>
| Verb | What it does |
|---|---|
status |
Whether the GitOps engine (Flux) is installed and ready |
discover |
Helm releases and GitOps engine state on the cluster |
preview |
Render the GitOps layout that would be written (non-mutating) |
export |
Write the layout to a repository (direct push, or --create-pr) |
enable |
Bootstrap Flux on the cluster against a repository |
disable |
Remove Flux from the cluster |
For enable and export, --repo is the repository in owner/repo form (for example acme/clusters), not a URL.
Validated end to end against a real Flux install on a tenant cluster: all verbs pass, the tenant stays healthy through enable and disable.
Delta since v0.11.0
- feat(cli): cluster gitops lifecycle commands (#52)