WIP: Used fixed API for Job Pod Failure Policy

[mimowo]

Bump the k8s/api to use the cherry-picks of the fix in kubernetes/kubernetes#126046 - it is going to released in 1.30.4 and 1.29.8, so for now using hash pointing to kubernetes/api@7c71f3c, which includes kubernetes/api@a63486c.

WIP because we probably want to wait until full release.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mimowo
Once this PR has been reviewed and has the lgtm label, please assign ahg-g for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubernetes-sigs-jobset canceled.

Name	Link
🔨 Latest commit	a630811
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-jobset/deploys/669f75eb4596af0008d79747

[mimowo]

/cc @danielvegamyhre @kannon92

[kannon92]

LGTM but I think it would be best to wait for official patch release also.

@danielvegamyhre any objections?

[danielvegamyhre]

LGTM but I think it would be best to wait for official patch release also.

@danielvegamyhre any objections?

I would prefer to watch for an official patch release as well, using a feature branch is a bit hacky and I want to prioritize production readiness and good engineering practices. The target date for 1.30.4 is 08-13-2024 which isn't an unreasonably long time. This bug is blocking the main use case of JobSet's new configurable failure policy (i.e., pairing JobSet failure policy rules with Pod failure policy rules to define more targeted restart/failure handling behavior), but I think we can wait until mid August for 0.6.0 release, and in the meantime perhaps include other important changes in 0.6.0, such as #618

[danielvegamyhre]

Closing this in favor of waiting for proper patch release, see #620 (comment)

[mimowo]

Closing this in favor of waiting for proper patch release, see #620 (comment)

Sure, makes sense. I opened it mostly to demonstrate e2e that the coming fix works. For the fix you can either use patch release of 1.29.8 or 1.30.4 .