Stages
- Actions
Typed pre, post, and on-failure steps — jobs, HTTP gates, waits, patches, deletes, transient applies.
- Conflict policies
Resolve immutable-field and ownership conflicts per resource.
- DependencyNotReady
A StageSet named in spec.dependsOn is not yet Ready.
- From Jsonnet to a gated rollout
Write Jsonnet manifests, render them with JaaS, and roll them out with StageSet — end to end.
- Producer-aware sources
Reference a producer like JaaS and let the controller find its ExternalArtifact.
- Progressive delivery
Gate a Flagger or Argo Rollouts promotion on a StageSet stage, and gate a StageSet stage on a Rollout.
- Ready checks
Gate a stage on health with kstatus and CEL expressions.
- Rollback
Restore the last good artifact revision when a run fails.
- StageFailed
A stage failed to fetch, build, apply, verify, or run an action; the run halts there.
- StageInventory
The controller-managed inventory of objects each stage applied.
- Stages and sources
The core — ordered stages applying Flux sources, with path, prune, patches, and substitution.
- StageSet
Every field of the StageSet resource — the one you author.
- StageSet vs Argo Rollouts
Different layers — staged multi-artifact delivery versus single-workload traffic shifting.
- StageSet vs Flux kustomize-controller
Intra-release stages and gates versus per-Kustomization ordering.
- StageSet vs Helm
How StageSet relates to Helm's templating and hook ordering.
- StageSet vs jsonnet-controller
A jsonnet-native Flux applier versus a renderer-agnostic staged-delivery layer.
- StageSet vs Kustomize
Why StageSet delivers what Kustomize only builds.
- StageSet vs Tanka and kubecfg
Reconciled, gated delivery versus CLI-driven Jsonnet apply.
- stagesetctl build
Render a StageSet's manifests to stdout, exactly as the controller would.
- stagesetctl diff
Preview what a StageSet would change in the cluster — usable as a CI gate.
- stagesetctl get
Print human-readable StageSet status, or list StageSets.
- stagesetctl reconcile
Force an out-of-band reconcile, optionally waiting for it to be handled.
- Stalled
The run cannot make progress and will not retry until the spec changes.
- Succeeded
All stages applied and verified the healthy steady state.
- Update windows
Allow or deny rollouts on a schedule, without pausing reconciliation.