Skip to content
Latchkey

What Is Canary Ingress Routing?

Canary ingress routing uses the ingress controller to split incoming traffic between the current version and a canary version by weight or header. A small percentage goes to the canary first, and the share increases as metrics confirm health. The ingress layer is the routing point, so no client changes are needed to shift traffic.

Why it matters

Routing a slice of real traffic exposes problems that staging cannot, while limiting the number of users affected. Gradually raising the weight turns a risky release into a measured, reversible rollout.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →