whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix description about document (#8613)

Browse Source 
I have tested with kubectl 1.10 and kubectl in master branch, completed
job pods show up in output.
This commit is contained in:
CaoShuFeng
2018-05-31 08:09:57 -04:00
committed by k8s-ci-robot
parent c0e874226e
commit ca8516dfcc
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
+1 -2
View File
@@ -205,8 +205,7 @@ policy for the embedded template to "`Never`".
## Job Termination and Cleanup ## Job Termination and Cleanup
When a Job completes, no more Pods are created, but the Pods are not deleted either. Since they are terminated, When a Job completes, no more Pods are created, but the Pods are not deleted either. Keeping them around
they don't show up with `kubectl get pods`, but they will show up with `kubectl get pods -a`. Keeping them around
allows you to still view the logs of completed pods to check for errors, warnings, or other diagnostic output. 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 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. 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.