Continuous Deployment: The GitOps, The Pipelines, and The Ugly
summary
Explains actual tradeoffs: push pipelines build images and push with credentials while GitOps tools pull and reconcile; demo installs Argo CD, creates applications, flips autosync on and shows git change driving replicas 1→3→0 back to 3 and a 0.1→0.2 image rollout working in ~20s checks. Reports failures: Flux once removed itself and a bad change required 2–3 hours of manual secret work to recover, and large installs (≈1,000 apps) push UI/sync time to ~7 minutes.
AI-written summary · about
chapters (19)
- 0:00Continuous Deployment intro
- 2:14Anti-patterns in deployments
- 5:29CI/CD and its role
- 8:01Issues with pipelines
- 11:37GitOps pull-based approach
- 13:25GitOps principles
- 17:46Demo setup Argo CD install
- 21:50Creating Argo CD apps
- 26:32Syncing and managing apps
- 29:04Auto-sync and pruning resources
- 31:36Manual changes reconciliation
- 33:02Helm charts and customizations
- 35:12Automated deployment customization
- 36:56GitOps repo best practices
- 37:20Summary and closing
- 37:43Q&A: Argo CD vs Flux
- 39:30Q&A: GitOps mistakes
- 40:58Q&A: Multi-cluster setup
- 41:22Q&A: Preserving resources
related talks
40mHow GitOps Changes Everything in CI/CD
37mDevelopers Love GitOps
06mGitOps - At a Glance
57mPipelines: Everything Everywhere All At Once
30mThe Intersection of CD Gates and GitOps: A Match Made in Deployment Heaven
35mPanel: GitOps User Stories
31mLeveraging GitOps to wrangle your clusters and projects
23mGitOps: yea or nay?