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

[heyleke]

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 kubernetes/enhancements#2214

We can clarify that it will be aborted.

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

[alculquicondor]

As for why the note was added...
Due to the async nature of kubernetes, it's possible that we don't observe the creation of Pods in a timely manner. We have some in-memory guards in place to prevent double creation. So it's very unlikely that you would observe such behavior but we simply don't make guarantees.

Not sure how to express all of the above in a user-friendly way :) I'll wait for suggestions from tech-writers.

[sftim]

/sig apps
/language en

Help wanted, but this isn't necessarily easy enough to merit /help

/remove-kind bug
/triage accepted

[sftim]

Thanks for the report @heyleke

[sftim]

/priority backlog

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[alculquicondor]

I know of one instance kubernetes/kubernetes#109429. I think it's about the garbage collection, but I don't have enough evidence.

/lifecycle frozen

[wu0407]

It occurrence many times in my cluster.
kubernetes/kubernetes#109429 (comment)

[mrgiles]

/assign

[mrgiles]

/unassign

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted