Progressive Delivery: The Logical Evolution CI/CD
summary
Progressive delivery sits on top of CI/CD and lets teams test changes in real production by combining feature flags, canary traffic split, blue/green, shadowing and A/B experiments. Practical steps: convert a Deployment to an Argo Rollout, change strategy to Canary, create two services and wire automated analysis templates (Datadog/Prometheus checks) to gate promotion. Case studies note AWS/large orgs phase rollouts over waves and Facebook-like teams spend ~1 year proving stateless flows; a healthcare rollout using canaries and traffic splitting succeeds when observability and automated rollback are in place.
AI-written summary · about
chapters (9)
- 0:00Introduction to speakers
- 1:27Professional backgrounds
- 2:10Defining progressive delivery
- 3:20Importance of testing in production
- 5:23Modern testing strategies
- 7:10Deployment vs release
- 8:46Progressive delivery techniques
- 14:23Implementation and best practices
- 18:17Tools and closing
related talks
35mProgressive Delivery with Argo Rollouts
51mProgressive Delivery in the Kubernetes era
46mProgressive Delivery in the Kubernetes era
38mProgressive Delivery: Patterns & Benefits of Decoupling Deploy from Release
01h 27mProgressive Delivery with Argo Rollouts
36mProgressive Delivery in the Kubernetes era
28mCross-Cluster Progressive Delivery: Rolling Out Apps With Arg...
16mProgressive Delivery with Observability