Kargo

ArgoCD answers “does this environment match its Git state.” Kargo answers a different question: “should this change move from staging to production yet” — and it’s the tool I’ve rolled out in production, from the first pilot promotion path through version upgrades and onboarding other teams onto it.

Where it fits

Kargo sits downstream of ArgoCD, not in competition with it — it owns the promotion path between environments once ArgoCD has already reconciled each one to its own Git state. Without it, promotion tends to mean someone manually editing a tag in a values file; with it, promotion becomes a first-class, auditable workflow.

Principles that hold up

• Verification stages before promotion, not after. A change should pass whatever checks matter (smoke tests, a soak period, manual approval) before it’s promoted to the next environment, not be promoted first and validated in place.
• Approvals as part of the workflow, not a side channel. A promotion approved in Kargo is visible and auditable in the same place the promotion itself happens — not a Slack thread or a verbal “go ahead” divorced from the actual change record.
• Promotion is the artifact worth keeping. The record of what moved from staging to production, when, and after what verification, is worth as much as the deployment itself — it’s what makes “what’s actually in production and why” answerable months later.

See ArgoCD for how each environment stays reconciled to Git in the first place.