If you delete a Deployment, what happens to its linked ReplicaSets?

If you delete a Deployment, what happens to its linked ReplicaSets?

• A. They are deleted along with the Deployment
• B. They remain running
• C. They become independent and must be cleaned up manually
• D. They are scaled down to zero but remain

Answer: (A)

Deleting a Deployment removes the resources it owns, and that includes the ReplicaSets it manages. The Deployment creates and owns its ReplicaSets, and those ReplicaSets, in turn, create Pods. When the Deployment is deleted, Kubernetes’ garbage collector deletes those dependent ReplicaSets (and the Pods they control) as part of cascading deletion. So the ReplicaSets don’t keep running or become independent, and they aren’t simply scaled down to zero—they’re removed along with the Deployment. If you wanted to keep the ReplicaSets, you’d need to delete them manually or change the deletion propagation policy.

Deleting a Deployment removes the resources it owns, and that includes the ReplicaSets it manages. The Deployment creates and owns its ReplicaSets, and those ReplicaSets, in turn, create Pods. When the Deployment is deleted, Kubernetes’ garbage collector deletes those dependent ReplicaSets (and the Pods they control) as part of cascading deletion. So the ReplicaSets don’t keep running or become independent, and they aren’t simply scaled down to zero—they’re removed along with the Deployment. If you wanted to keep the ReplicaSets, you’d need to delete them manually or change the deletion propagation policy.