Rethinking Continuous Delivery
summary
MacPaw consolidated deployment from 30 app pipelines into one infrastructure repository so upgrades (Helm, GCR) and security changes need a single commit. They implemented GitOps using Flux and Argo Events to create per-PR dynamic namespaces, perform Helm post-rendering, and run an image-reflector/updater flow to provide preview environments, while facing challenges with asynchronous events, developer notifications, and some tool limitations.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:25Classic CD problems
- 7:05Security and org challenges
- 11:02Switching to Flux
- 16:30New Flux deployment scheme
- 21:49Handling PRs in dynamic envs
- 28:16Preview envs with Argo Events
- 33:21Q&A
- 37:38Infrastructure resources
- 40:30Architecture questions
- 43:21CD approach evolution
- 44:26Optimizing Preview envs
related talks
43mContinuous Deployment: The GitOps, The Pipelines, and The Ugly
35mPanel: GitOps User Stories
37mDevelopers Love GitOps
33mGitOps Pipelines: Everything Everywhere All at Once
40mHow GitOps Changes Everything in CI/CD
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
22mPush to Prod: GitOps Workflows on k8s with FluxCD
