What happens when you delete a Kubernetes Deployment?

What happens when you delete a Kubernetes Deployment?

• A. Both the Deployment and the linked ReplicaSets are deleted
• B. Only the Deployment is deleted
• C. Only the ReplicaSets are deleted
• D. The deletion is a soft delete and resources are cleaned up later

Answer: (A)

Deleting a Deployment removes the object that manages the workload and also cleans up the resources it controls. The Deployment creates ReplicaSets, and those ReplicaSets (and their Pods) are owned by the Deployment. When you delete the Deployment, Kubernetes’ garbage collector removes the owned ReplicaSets, which in turn deletes their Pods. This is why both the Deployment and the linked ReplicaSets end up deleted. If you wanted to keep the ReplicaSets or Pods, you’d need to delete them separately or disable cascading deletion.

Deleting a Deployment removes the object that manages the workload and also cleans up the resources it controls. The Deployment creates ReplicaSets, and those ReplicaSets (and their Pods) are owned by the Deployment. When you delete the Deployment, Kubernetes’ garbage collector removes the owned ReplicaSets, which in turn deletes their Pods. This is why both the Deployment and the linked ReplicaSets end up deleted. If you wanted to keep the ReplicaSets or Pods, you’d need to delete them separately or disable cascading deletion.