a6-recipe-canary

Overview

A canary release gradually shifts traffic from the stable version to a new version. Start with a small percentage (e.g., 5%), monitor for errors, then increase incrementally until the new version receives 100% of traffic. If errors spike at any stage, roll back instantly.

This recipe uses the traffic-split plugin to manage weighted traffic distribution between stable and canary upstreams.

When to Use

• Deploy new versions with minimal blast radius
• Validate changes with real production traffic before full rollout
• You need gradual rollout with monitoring checkpoints
• You want automatic or scripted rollback on error detection