Pushing Code: Don't Forget to Flag Your Canaries?
summary
Iterative canarying reduces blast radius by releasing in 25% rollouts tied to feature flags, letting teams monitor spikes in Prometheus and Sumo Logic and roll back quickly. The team builds a communications tool called comsflow and uses phased user cohorts to gain production readiness and feedback, which speeds the roadmap but creates work: missing flag owners, necessary code cleanup, and explicit rollback plans emerge as concrete followups.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:28Reliability matters most
- 3:57Four golden signals
- 7:08Iterative releases with canaries
- 10:17Canary release and why use it
- 12:03Canary releases lifecycle
- 13:47Canary release process
- 15:55Feature flags for rollouts
- 17:43ComsFlow case study
- 20:09Lessons from ComsFlow
- 22:37Choosing canary user groups
- 24:20Benefits of canary deployments
- 25:02Q&A
related talks
20mHow We Progressively Deliver Changes To Kubernetes Using Canary Deployments and Featur...
01h 04mThe Fine Art of Canary Deployments
35mReduce Risks With Continuous...
59mFaster & less risky releases with feature flags
21mTesting in Production
13mCanary in the Internet Mine
38mTesting in Production
20mProgressive Delivery with the Kubernetes Gateway API