Canary Routing Template
Use this template to gradually shift traffic to a new backend version.
Default pattern
http_trigger -> condition_node (canary?) -> backend-new/backend-stable -> response_node
Configure
- Define canary selection rule (header/tenant/feature flag/percentage).
- Route canary branch to new backend and default branch to stable backend.
- Add response/log marker for branch visibility.
- Roll out progressively based on latency/error health.
Verify
- Forced canary request reaches new backend
- Non-canary request stays on stable backend
- Error trend remains acceptable before traffic increase