When a Deployment's image is updated, what is created to track the new version?

When a Deployment's image is updated, what is created to track the new version?

• A. A NEW Pod
• B. A NEW Namespace
• C. A NEW ReplicaSet
• D. A NEW Service

Answer: (C)

When a Deployment image is updated, Kubernetes creates a new ReplicaSet to manage the updated Pod template. This new ReplicaSet is responsible for spawning the updated Pods and maintaining the desired count for that version. The Deployment then rolls out the change by scaling up the new ReplicaSet and scaling down the old one according to the rolling update strategy. A new Pod is created as part of the new ReplicaSet, but the object that tracks the new version is the new ReplicaSet itself. A new Namespace or a new Service isn’t created as part of an image update; they serve separate purposes and aren’t tied to versioning.

When a Deployment image is updated, Kubernetes creates a new ReplicaSet to manage the updated Pod template. This new ReplicaSet is responsible for spawning the updated Pods and maintaining the desired count for that version. The Deployment then rolls out the change by scaling up the new ReplicaSet and scaling down the old one according to the rolling update strategy. A new Pod is created as part of the new ReplicaSet, but the object that tracks the new version is the new ReplicaSet itself. A new Namespace or a new Service isn’t created as part of an image update; they serve separate purposes and aren’t tied to versioning.