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

Better description of Job execution

Browse Source 
Just a small clarification on the description of the responsibilities of a Job. Kubernetes doesn't ensure that the Pods are successful, but the scheduler's responsibility is to continue retrying until success. Updating the docs with a slight wording change to more accurately reflect that a Job won't ensure success, but it will continue retrying until success.
This commit is contained in:
Marc Campbell
2021-01-25 12:57:00 -08:00
committed by GitHub
parent 6ce3a86545
commit 8a48273855
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/job.md
+1 -1
View File
@@ -13,7 +13,7 @@ weight: 50
<!-- overview --> <!-- overview -->
A Job creates one or more Pods and ensures that a specified number of them successfully terminate. A Job creates one or more Pods and will continue to retry execution of the Pods until a specified number of them successfully terminate.
As pods successfully complete, the Job tracks the successful completions. When a specified number As pods successfully complete, the Job tracks the successful completions. When a specified number
of successful completions is reached, the task (ie, Job) is complete. Deleting a Job will clean up of successful completions is reached, the task (ie, Job) is complete. Deleting a Job will clean up
the Pods it created. the Pods it created.