Multi-Stage Deployment Pipelines the GitOps Way
summary
Kargo offers a declarative orchestrator that promotes artifacts between stages by committing to Git and triggering Argo CD syncs, handling container images, Helm charts and raw manifests, and rendering with Kustomize or Helm. It models stages like Dev, Staging, parallel AB-test A/B, and Prod regions London/Paris/Zurich, tracks a Freight line of candidates, performs manual or automated promotions (it makes per-environment git commits, e.g. three commits to three prod repos), and provides a control flow stage for coordinated rollouts while promising rollbacks and verification hooks.
AI-written summary · about
chapters (7)
- 0:00Multi-stage GitOps pipelines
- 2:08Promoting changes between stages
- 7:05CI vs CD tasks
- 7:48Cargo for GitOps
- 9:13Demo: Cargo in action
- 18:34Cargo roadmap and community
- 19:57Closing and resources
related talks
06mMulti-Stage Deployment Pipelines the GitOps Way
07mNavigating Multi-stage Deployment Pipelines via the GitOps Approach
33mGitOps Pipelines: Everything Everywhere All at Once
57mPipelines: Everything Everywhere All At Once
33mProgressive Infrastructure Delivery using Kargo and Argo CD
57mGitOps: From Commit to Deploy
16mUse Kubernetes-native Integrated GitOps CI/CD Workflows
09mBehind the Curtain: Multi-Cluster Backstage Deployments with GitO...