canary release
Sending a small share of real traffic to a new version first, and increasing it only while its metrics stay healthy.
In more detail
The stable version keeps serving the rest and is the comparison. Each step needs a threshold that stops the rollout, and rollback sets the canary's share back to zero.
Examples
25 25 percent0.0089 4.45 abort and roll backA typical schedule is 10%, then 25%, then 50%, then 100%.Related terms
- baseline — A reference measurement that later measurements are compared against.
- blast radius — How much of a system is affected when something fails or has to be running for a check to happen.
- quality gate — A check, or set of checks, that a change must pass before it can move on, such as being merged or promoted to the next pipeline stage.
- rolling update — Replacing instances of an application with the new version a few at a time while the rest keep serving.
- Argo Rollouts — A Kubernetes controller that adds canary and blue-green strategies through a Rollout object that replaces a Deployment.
- setWeight — An Argo Rollouts canary step that sets the percentage of traffic sent to the new version.
- stable version — The currently released version that keeps serving most traffic during a canary and is the baseline for comparison.
- error rate — The share of requests that fail, reported alongside latency so a fast result is not mistaken for a healthy one.
- progressive delivery — Releasing a new version to a growing share of users step by step, checking health at each step before going further.
- traffic splitting — Dividing incoming requests between two versions by percentage.
- rollback — Returning a system to a previous known-good version after a bad change.
Taught in
- Two Hundred Accounts And One Bad Deploy — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Surviving A Hundred And Eighty Minutes — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- CodeDeploy: Hooks That Never Ran — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Strategies Across Compute: The Canary That Saw Nothing — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- StackSets: Eighty Failures Before Lunch — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Systems Manager At Fleet Scale: Compliant And Unpatched — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Long-Stem Clinic: When Two Answers Both Work — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Blue-Green, Canary, Rings And Feature Flags — Microsoft Azure DevOps Engineer Expert (AZ-400) Exam Prep
- One Commit, Four Argo Projects — Certified Argo Project Associate (CAPA) Exam Prep
- The Rollout: A Deployment That Can Stop Halfway — Certified Argo Project Associate (CAPA) Exam Prep
- Canary And Blue-Green: Weights, Routers And One Switch — Certified Argo Project Associate (CAPA) Exam Prep
- AnalysisTemplate And AnalysisRun: Letting Metrics Decide — Certified Argo Project Associate (CAPA) Exam Prep
- Final Mock, Review And A Trap Sprint — Certified Argo Project Associate (CAPA) Exam Prep
- Related Practices Sprint: One Change, Five Practices — Certified GitOps Associate (CGOA) Exam Prep
- Thursday, With A Way Back: Promotion, Deploy And Release — Certified GitOps Associate (CGOA) Exam Prep
- Friday, Four Fifty: Progressive Delivery — Certified GitOps Associate (CGOA) Exam Prep
- Patterns Sprint: Eight Needs, One Pattern Each — Certified GitOps Associate (CGOA) Exam Prep
- Forty-Six Of Sixty: The Mock And What It Tells You — Certified GitOps Associate (CGOA) Exam Prep
- The Evening Before: Final Review — Certified GitOps Associate (CGOA) Exam Prep
- Introduction to Release Strategies — Continuous Integration & Continuous Delivery Pipelines
- Canary Releases — Continuous Integration & Continuous Delivery Pipelines
- Build, Release, Run And Processes — DevOps & Site Reliability Engineering
- Deployment Strategies: Blue Green — DevOps & Site Reliability Engineering
- Deployment Strategies: Canary Releases — DevOps & Site Reliability Engineering
- Decoupling Release From Deployment: Feature Flags — DevOps & Site Reliability Engineering
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- Continuous Delivery: Blue-Green & Canary Pipelines — Production Full-Stack Engineering
References
- Danilo Sato on martinfowler.com: CanaryRelease
- Google SRE workbook: Canarying Releases
- Argo Rollouts: Canary deployment strategy
- Argo Rollouts: Canary