From 1a2e20268a77173aecc08fbc3fff983ded512b81 Mon Sep 17 00:00:00 2001 From: Chris Jones Date: Thu, 29 Jul 2021 12:50:06 -0600 Subject: [PATCH] Add a clarifying reference about a Job's Pod deletion. --- content/en/docs/concepts/workloads/controllers/job.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md index 5fd1a89c56..3471feaa1f 100644 --- a/content/en/docs/concepts/workloads/controllers/job.md +++ b/content/en/docs/concepts/workloads/controllers/job.md @@ -255,7 +255,8 @@ from failed Jobs is not lost inadvertently. ## Job termination and cleanup -When a Job completes, no more Pods are created, but the Pods are not deleted either. Keeping them around +When a Job completes, no more Pods are created, but the Pods are [usually](#pod-backoff-failure-policy) not deleted either. +Keeping them around allows you to still view the logs of completed pods to check for errors, warnings, or other diagnostic output. The job object also remains after it is completed so that you can view its status. It is up to the user to delete old jobs after noting their status. Delete the job with `kubectl` (e.g. `kubectl delete jobs/pi` or `kubectl delete -f ./job.yaml`). When you delete the job using `kubectl`, all the pods it created are deleted too.