When a CronJob is deleted, what happens to the associated jobs and pods?

When a CronJob is deleted, what happens to the associated jobs and pods?

• A. They are deleted along with the CronJob
• B. They are preserved for audit
• C. They are moved to the default namespace
• D. They are terminated and removed independently

Answer: (A)

The key idea is ownership and automatic cleanup. A CronJob creates Jobs, and those Jobs (and the Pods they run) are owned by the CronJob through owner references. When the CronJob is deleted, Kubernetes’ garbage collection removes resources that are owned by it, so the dependent Jobs and the Pods they created are deleted as well. This prevents leftover Jobs from persisting after the CronJob is gone. If you want to keep the Jobs, you’d need to disable cascading deletion or delete them manually.

The key idea is ownership and automatic cleanup. A CronJob creates Jobs, and those Jobs (and the Pods they run) are owned by the CronJob through owner references. When the CronJob is deleted, Kubernetes’ garbage collection removes resources that are owned by it, so the dependent Jobs and the Pods they created are deleted as well. This prevents leftover Jobs from persisting after the CronJob is gone. If you want to keep the Jobs, you’d need to disable cascading deletion or delete them manually.