A canary deployment, or canary release, rolls out a change to a small, controlled subset of production before a wider deployment. It limits the blast radius if the change fails. This approach is especially suited to environments with only a few production instances. section 6.14.2
Canary releases are one way to control rollout risk:
- Feature flags turn functionality on or off without another deployment, supporting experiments and quick rollbacks. section 6.14.2
- Progressive rollouts gradually expand scope and are better suited to large deployments spanning multiple clusters or regions. section 6.14.2
- Shadow testing runs a change alongside production traffic without affecting real users, allowing correctness checks before it is enabled. section 6.14.2
A change to a critical dependency
Suppose a service has a hard dependency whose failure could cause a production incident. A limited rollout keeps the initial change small. Before expanding it, teams need to validate each step, check version compatibility, and have a tested rollback mechanism. A canary limits exposure; it does not replace those checks. section 6.14.2 section 7.5.1










