Canary deployment pipeline

A canary deployment reduces the initial exposure of a release by sending only a small share of production traffic to it. This diagram starts with pre-release tests, then deploys the candidate to five percent of traffic. The team watches explicit guardrails instead of treating deployment as the final step. Passing guardrails permits an expansion to twenty-five percent and a second observation period. Failing guardrails trigger removal of the canary and restoration of the prior version. A hold path gives the team time to investigate when the expanded rollout is not ready to continue. Replace the traffic percentages and measurements with the limits that match the service and its release policy.