DevOps · Flashcard
How does a canary release work with a mesh?
- AA small traffic share goes to the new version — it grows gradually as health metrics stay green
- BThe new version replaces all Pods at once — the mesh rolls back if startup probes fail
- CThe new version runs in a separate cluster — DNS switches over after a long soak period
- DBoth versions process every request — responses are compared and the faster one wins
Why this is the answer
Canarying shifts a small, adjustable percentage to the new version while watching metrics — the mesh makes the weights precise and instantly changeable. All-at-once replacement is a plain rolling update, separate-cluster DNS cutover is blue-green at the infrastructure level, and duplicate-processing describes mirroring, not canary.
Official docs