Cloud-Native Progressive Delivery
summary
Claims automated production-safe rollouts by separating deployment (running container images in Kubernetes) from release (exposing users), builds a controller that uses Flux, Flagger and Istio to do canaries, traffic mirroring and automated rollbacks, measures RED metrics (rate error duration) and ramps traffic (default 50/50 when naive, then controlled to 1% → gradual increase), lets testers opt in via headers, and reports if surprises appear (e g a 1% error budget breach or longer latency) before full release.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:5712 Factor Apps
- 6:24Docker
- 7:44Microservices
- 12:23Metrics
- 15:34Service Levels
- 17:46Service Mesh
- 22:57Continuous Deployment
related talks
32mCloud Native Progressive Delivery
16mProgressive Delivery with Flagger
51mProgressive Delivery in the Kubernetes era
33mProgressive Delivery Techniques with Flagger
36mProgressive Delivery in the Kubernetes era
46mKubernetes Native Continuous Deployment with FluxCD, Flagger, and Linkerd
22mProgressive Delivery: The Logical Evolution CI/CD
46mProgressive Delivery in the Kubernetes era
