Canary Deployments Are a Myth - True Progressive Delivery Occurs Via OpenFeature
Talkat OpenFeature Summit Europe 2025 · on Tuesday, 2025-04-01· at 14:30· Level 3 | ICC Capital Suite 2-4·
summary
Claims that canary deployments are a myth and that real progressive delivery is achieved with OpenFeature feature flags, not traffic-splitting. Uses Octopus Deploy’s cell-based architecture and release rings: staff → early adopters → customers, running four concurrent early-adopter programs to gather feedback. Trunk-based development with feature toggles keeps main deployable, feature branches average days not months, one large UI rev exposed issues that were paused per-instance, rollbacks happen via OpenFeature toggles allow rollback with a single switch, implemented in roughly a week for 90% of needs.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:13Canary deployments myth
- 7:29Host limits for canaries
- 10:35Canary use cases
- 12:47Octopus Deploy cells
- 14:49Deployment vs release
- 18:39Feature flags for delivery
- 21:49Flag challenges
- 23:36OpenFeature vs canaries
- 27:25Q&A
related talks
20mHow We Progressively Deliver Changes To Kubernetes Using Canary Deployments and Featur...
22mProgressive Delivery: The Logical Evolution CI/CD
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
51mProgressive Delivery in the Kubernetes era
24mSkip the Deployment Queue: Automated Rollouts and Rollbacks Using OpenFeature
44mFlagging features — a DevOps approach to continuous release
38mProgressive Delivery: Patterns & Benefits of Decoupling Deploy from Release
50mRings and Canaries - Advanced Deployment Scenarios