displayName
Canary Deployment
description
Infrastructure-level progressive deployment workflow that routes a small percentage
of live production traffic to a new service version while the majority continues to
hit the stable version. SRE and DevOps engineers configure traffic splitting in the
load balancer or service mesh, define canary success criteria (latency p99, error
rate, business KPIs), and set up automated rollback triggers. Observability tooling
continuously compares canary versus baseline metrics. If the canary is healthy over
a defined bake time, traffic shifts fully to the new version; if anomalies are
detected the canary is rolled back automatically. Minimises customer impact from
bad releases in complex distributed systems.
workflowKind
release
triggerType
on-demand
typicalCadence
per-release
complexity
complex