Traffic to a 311 API spikes overnight. The team needs more Pods but must not change the running container image. Which action correctly separates scale from a rolling image update?
Select an answer to reveal the explanation.
Short Explanation
Turning up more cashiers isn’t the same as rewriting the register software. Scaling .spec.replicas (or kubectl scale) adds capacity on the current template; leave the image alone unless you intentionally want a rollout.
Full Explanation
Deployment replica count and Pod template are independent controls. Updating .spec.replicas scales the current ReplicaSet without requiring an image change. Changing the container image updates the Pod template and starts a rolling update. Deleting the Service or misusing maxSurge as a substitute for .spec.replicas does not correctly express desired capacity.