A Million Ways To Promote Changes Between Environments
summary
Compares concrete promotion patterns and what actually works: CI-driven pipelines that run argo sync and hang waiting for long canaries, Image Updater commits image updates to Git and needs CI for tagging, ApplicationSet progressive sync is alpha and requires disabling autosync so it can click sync in order, Cargo (Kargo) groups artifacts into freights and stages with analysis templates, Telephonit just copies folders, Codefresh Githops diffs and commits promotable paths, and GitOps Promoter plus source hydrator renders manifests to branches auto-creates and merges PRs; rendered manifests reduce mismatch but cluster flapping and how to trigger downstream SDLC steps remain unresolved.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:49What promotions mean
- 5:00Manual promotion process
- 6:04GitOps promotion challenges
- 8:32Promotion tools overview
- 10:39Argo CD Application Set sync
- 12:01Argo CD Image Updater
- 12:43Argo CD Freight multi-stage
- 14:08Telephonit replication
- 15:30Codefresh GitOps promotions
- 18:00GitOps Promoter hydrator
- 21:51Promotion tools philosophies
- 23:57Promotion best practices
- 26:43Resources and closing
related talks
24mBest Practices for GitOps Promotions
59mPromotion Between Environme...
05mApplication promotion in GitOps
28mClick-Free Environment Promotion Driven by ApplicationSets Progre...
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
37mPanel: Navigating Promotions: Insights From the Argo Community
57mPipelines: Everything Everywhere All At Once
29mCombining Progressive Delivery with GitOps and Continuous Delivery