kubernetes / kubernetes/website

Job completion-mode documentation has an unclarified note about a 'rare' condition

Open
#31,719 10 comments 0 reactions 0 assignees View on GitHub
language/en lifecycle/frozen needs-triage priority/backlog sig/apps
Dominant language
HTML
Stars
5.4k
Forks
15.7k
Avg merge
4d 18h
Merged PRs (30d)
204

Description

**This is a Bug Report**

**Problem:**
https://kubernetes.io/docs/concepts/workloads/controllers/job/#completion-mode mentions

> Note that, although rare, more than one Pod could be started for the same
> index, but only one of them will count towards the completion count.

Can it be clarified why that note is needed? And if the pod is started, will it run to completion, or aborted before running or ... ?

**Proposed Solution:**
@alculquicondor proposes via https://github.com/kubernetes/enhancements/issues/2214

> We can clarify that it will be aborted.

**Page to Update:**
https://kubernetes.io/docs/concepts/workloads/controllers/job

Contributor guide

Open the contributing guide

Research direction

Start with the completion-mode section on the Job documentation page and read enhancement issue 2214 for the proposed clarification. Update the note so the behavior of the extra Pod is explicit, including that it will be aborted, and verify the page answers why the condition matters.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.