A team calls every Deployment rolling update a “canary.” What distinction should they learn?
Select an answer to reveal the explanation.
Short Explanation
Rolling update is swapping seats row by row in one theater. Canary is opening a tiny second theater and sending a few patrons there on purpose. Same building (Kubernetes), different show plans—don’t mash the words together.
Full Explanation
A Deployment rollingUpdate strategy replaces Pods within a single Deployment’s ReplicaSets over time. A canary release intentionally runs a small additional Deployment (or replica set) that shares Service traffic for evaluation. maxUnavailable alone does not redefine rolling as canary, and Jobs are not the canary vehicle for long-lived services.