An ops note says changing only a Deployment annotation can record a change-cause, while Pod template changes drive rollouts. Which statement is accurate for when a new rolling update begins?
Select an answer to reveal the explanation.
Short Explanation
Sticky notes on the folder aren’t the same as rewriting the recipe inside. Annotate for change-cause documentation; change the Pod template—image, env, probes—and that’s what actually spins a new ReplicaSet.
Full Explanation
A Deployment creates a new ReplicaSet when the Pod template hash changes—typically from image, command, env, volume, or probe edits under .spec.template. Metadata annotations on the Deployment can document kubernetes.kubernetes.io/change-cause for rollout history without replacing Pods by themselves. Selector changes are constrained after creation, and ConfigMap content updates do not automatically restart Pods unless the Pod template or a reload mechanism changes.