Canary deployments (releasing a new version to a small group first) need precise traffic splitting. A small share of traffic goes to the new version, and the rest goes to the stable baseline. This article shows how I built that inside PipeCD's Kubernetes multi-cluster plugin: how the routing logic works, why there is a baseline variant next to canary, and the specific challenges of making it work across clusters.
Read the full article on dev.to.