Add more granular failure reason for Job PodFailurePolicy

[danielvegamyhre]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add an optional Reason field to the Job PodFailurePolicyRule, which allows the user to specify the failure reason which will be included in the condition added to the Job when it fails.
• Kubernetes Enhancement Proposal:
• Discussion Link: Publish finer-grained failure reason for podFailurePolicy kubernetes#122972
• Primary contact (assignee): @danielvegamyhre
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.31
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4443: Configurable Job failure reason for PodFailurePolicyRule #4479
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[danielvegamyhre]

/sig apps
/wg batch

[soltysh]

/label lead-opted-in
/milestone v1.30
/stage alpha

[salehsedghpour]

Hello @danielvegamyhre 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage alpha for v1.30 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.30.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, we would just want to update the following but it's not required for alpha stage and it will serve for future stages:

• Make sure that the KEP-4443: Configurable Job failure reason for PodFailurePolicyRule #4479 is merged to the k/enhancements repo.

The status of this enhancement is marked as At risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well, I couldn't find any related PR regarding this KEP in k/enhancements. Thank you!

[salehsedghpour]

Hello 👋, 1.30 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in 1.30, please file an exception request. Thanks!

[salehsedghpour]

/milestone clear

[soltysh]

/label lead-opted-in
/milestone v1.31
/stage alpha