Skip to content

Commit ca366f7

Browse files
committed
Add note for multiple pods for same job index
1 parent 943171c commit ca366f7

File tree

1 file changed

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

1 file changed

+8
-2
lines changed

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

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -290,8 +290,14 @@ Jobs with _fixed completion count_ - that is, jobs that have non null
290290
The Job is considered complete when there is one successfully completed Pod
291291
for each index. For more information about how to use this mode, see
292292
[Indexed Job for Parallel Processing with Static Work Assignment](/docs/tasks/job/indexed-parallel-processing-static/).
293-
Note that, although rare, more than one Pod could be started for the same
294-
index, but only one of them will count towards the completion count.
293+
294+
{{< note >}}
295+
Although rare, more than one Pod could be started for the same index (due to various reasons such as node failures,
296+
kubelet restarts, or Pod evictions), but only one of them will count towards the completion count.
297+
In this case, only the first Pod that completes successfully will count towards the completion count and
298+
update the status of the Job. The other Pods that are running or completed for the same index will be
299+
deleted by the Job controller once they are detected.
300+
{{< /note >}}
295301

296302

297303
## Handling Pod and container failures

0 commit comments

Comments
 (0)