Cloud Native Progressive Delivery
summary
Argues that cloud native lets teams decouple deployment from release by running new container images in prod while routing users to the known-good version, using Kubernetes plus Istio service mesh for network control, flux gitops to sync manifests and a Flagger canary operator to automate canaries, ramps and rollbacks. Demo shows images 1.0, 1.0.1 and 1.1 deployed, tests and traffic mirroring run in prod, and automated metric-based ramping (start at 1% then auto-increase) with SLO-based gating.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:40How does cloud native enable this?
- 10:33Deployment = Release?
- 11:10Build
- 11:54Deploy
- 18:18Release
- 19:37Demo
- 31:36Outro
related talks
38mCloud Native Progressive Delivery
43mCloud-Native Progressive Delivery
51mProgressive Delivery in the Kubernetes era
35mLeveling Up Your CD: Unlocking Progressive Delivery on Kubernetes
35mCloud Native Development Without the Toil
36mProgressive Delivery in the Kubernetes era
46mProgressive Delivery in the Kubernetes era
16mProgressive Delivery with Flagger