Which resource is created to manage the replicas for a Deployment?

Which resource is created to manage the replicas for a Deployment?

• A. Pod
• B. ReplicaSet
• C. Service
• D. Node

Answer: (B)

In Kubernetes, a Deployment expresses the desired state for a group of pods, including how many replicas should run and the pod template. It doesn’t create pods directly; it creates and manages a ReplicaSet that enforces that replica count. The ReplicaSet ensures the specified number of pods with the matching labels are running at all times—creating new pods when others stop and scaling up or down as the Deployment changes. During updates, a new ReplicaSet is created with the updated template and the Deployment shifts traffic between the old and new sets in a rolling fashion, with old ReplicaSets kept for potential rollback. Other resources don’t manage pod replicas: a Pod is the running instance, a Service exposes pods, and a Node is a worker machine. So the resource created to manage the replicas for a Deployment is the ReplicaSet.

In Kubernetes, a Deployment expresses the desired state for a group of pods, including how many replicas should run and the pod template. It doesn’t create pods directly; it creates and manages a ReplicaSet that enforces that replica count. The ReplicaSet ensures the specified number of pods with the matching labels are running at all times—creating new pods when others stop and scaling up or down as the Deployment changes. During updates, a new ReplicaSet is created with the updated template and the Deployment shifts traffic between the old and new sets in a rolling fashion, with old ReplicaSets kept for potential rollback. Other resources don’t manage pod replicas: a Pod is the running instance, a Service exposes pods, and a Node is a worker machine. So the resource created to manage the replicas for a Deployment is the ReplicaSet.