Skip to content

Commit 8a48273

Browse files
authored
Better description of Job execution
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.
1 parent 6ce3a86 commit 8a48273

File tree

1 file changed

+1
-1
lines changed
  • content/en/docs/concepts/workloads/controllers

1 file changed

+1
-1
lines changed

content/en/docs/concepts/workloads/controllers/job.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ weight: 50
1313

1414
<!-- overview -->
1515

16-
A Job creates one or more Pods and ensures that a specified number of them successfully terminate.
16+
A Job creates one or more Pods and will continue to retry execution of the Pods until a specified number of them successfully terminate.
1717
As pods successfully complete, the Job tracks the successful completions. When a specified number
1818
of successful completions is reached, the task (ie, Job) is complete. Deleting a Job will clean up
1919
the Pods it created.

0 commit comments

Comments
 (0)