Job success/completion policy

[tenzen-y]

Enhancement Description

• One-line enhancement description (can be used as a release note): An API to define when a Job can be declared as succeeded based on the number of succeeded pods.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3998-job-success-completion-policy
• Discussion Link: Job success/completion policy kubernetes#117600
• Primary contact (assignee): @tenzen-y
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.30
  • Beta release target (x.y): v1.31
  • Stable release target (x.y): v1.33
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3998: Job success/completion policy #4062
    • KEP-3998: Uptdate JobSuccessPolicy API Name and Validations #4537
  • Code (k/k) update PR(s):
    • Job: Support for the SuccessPolicy kubernetes#123412
    • Job: Use the fake clock in TestTrackJobStatusAndRemoveFinalizers kubernetes#123826
  • Docs (k/website) update PR(s):
    • Add JobSuccessPolicy Doc website#45135
    • KEP-3998: Rephrase JobSuccessPolicy documentations website#45677
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-3998: Graduate Job SuccessPolicy to Beta #4702
    • KEP-3998: Update the metrics and condition reason for the Beta graduation #4775
  • Code (k/k) update PR(s):
    • Job: Fix a bug that the SuccessCriteriaMet could be added to the Job with successPolicy regardless of the featureGate enabling kubernetes#125429
    • Job: Add the CompletionsReached reason to the SuccessCriteriaMet condition kubernetes#126074
    • Job: Introduce a new job_suceeded_total metric kubernetes#126075
    • Graduate the JobSuccessPolicy to beta kubernetes#126064
    • Graduate the JobSuccessPolicy to Beta kubernetes#126067
  • Docs (k/website) update PR(s): Update JobSuccessPolicy documentations for the beta graduation website#46970
• Stable
  • KEP (k/enhancements) update PR(s): KEP-3998: Graduate JobSuccessPolicy to GA #5148
  • Code (k/k) update PR(s):
    • KEP-3998: Promote JobSuccessPolicy to Stable kubernetes#130536
    • KEP-3998: Promote JobSuccessPolicy E2E to Conformance kubernetes#130658
  • Docs (k/website) update(s):
    • KEP-3998: Graduate JobSuccessPolicy to Stable website#49807
    • Placeholder for JobSuccessPolicy feature blog website#49998

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

/sig apps
/wg batch
/assign

[alculquicondor]

@soltysh I'm not sure if this will make it to the enhancements freeze, but would you consider a lead-opted-in?

[soltysh]

@soltysh I'm not sure if this will make it to the enhancements freeze, but would you consider a lead-opted-in?

Sorry, I won't be able to get there before today's freeze

[tenzen-y]

Since many discussions are left, I will try to complete it for the next release cycle (v1.29).
Thanks to everyone!

[dejanzele]

Hey @tenzen-y,

Are you still working on this KEP?

I just finished graduation of the PodReplacementPolicy to Beta and I have capacity to take on additional work if you don't have capacity to work on this KEP.

[tenzen-y]

KEP-3998: Job success/completion policy #4062

I'm working on this now. I will move this forward in the next release cycle (v1.30) since the enhancement freeze for this release (v1.29) came.

#4062 (comment)

[kannon92]

@soltysh since the KEP is being reviewed, did you consider adding this as a feature for sig-apps for 1.30?

[soltysh]

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

[pnbrown]

Hello @tenzen-y 👋, 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 need to update the following:

• Make sure the PR with the information get merged before enhancement freeze, I just found this PR.

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. Thank you!

[tenzen-y]

@pnbrown Thank you for contacting me.

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

This enhancement is still targeting for alpha stage. Could you confirm again?

[pnbrown]

That's my mistake. Editing now

[tenzen-y]

That's my mistake. Editing now

Thanks.

[pnbrown]

With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

[celestehorgan]

Hi @tenzen-y!

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[tenzen-y]

Hi @tenzen-y!

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

Sure. Thank you for reminding me!
Created: kubernetes/website#45135

[natalisucks]

Hi @tenzen-y,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository.
The placeholder PR deadline is 27th February, 2024.

Here's the 1.30 Release Calendar

[tenzen-y]

Hi @tenzen-y,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository. The placeholder PR deadline is 27th February, 2024.

Here's the 1.30 Release Calendar

@natalisucks Hi, thank you for contacting me. I created a placeholder PR here: kubernetes/website#45274.

[fykaa]

Hello @tenzen-y 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage stable for v1.33 (correct me, if otherwise)
/stage stable

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: v1.33.
• 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). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• Please update the latest-milestone to v1.33
• The PRR file should have the Stable stage listed with the approver details.

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[tenzen-y]

Hello @tenzen-y 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage stable for v1.33 (correct me, if otherwise) /stage stable

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: v1.33.[x] 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). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• Please update the latest-milestone to v1.33
• The PRR file should have the Stable stage listed with the approver details.

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

Thank you for reminding me. Let me open KEP updates PR ASAP

[tenzen-y]

@fykaa Hi, I opened the KEP there: #5148

[dipesh-rawat]

Hello @tenzen-y 👋, 1.33 Enhancements team here.

Now that PR #5148 has been merged, all the KEP requirements are in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

/label tracked/yes

[michellengnx]

Hello @tenzen-y 👋, v1.33 Docs Shadow here.
Does this enhancement work planned for v1.33 require any new docs or modification to existing docs?
If so, please follow the steps here to open a PR against dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[tenzen-y]

Hello @tenzen-y 👋, v1.33 Docs Shadow here. Does this enhancement work planned for v1.33 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

Thank you for pointing that out. I opened the placeholder PR: kubernetes/website#49807

[rytswd]

Hi @tenzen-y 👋 -- this is Ryota (@rytswd) from the 1.33 Communications Team!

For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 2025: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[fykaa]

Hey again @tenzen-y 👋, v1.33 Enhancements team here,

Just checking in as we approach Code Freeze at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, I couldn’t find any PR listed in the GitHub issue, neither can I find any associated PRs in kubernetes/kubernetes--could you please share the list of PRs that need tracking?

1. Please Update the Issue description to include all the related PRs of this KEP

If you anticipate missing code freeze, you can file an exception request in advance.
Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

The status of this enhancement is marked as At risk for code freeze.

As always, we are here to help if any questions come up. Thanks!

[rytswd]

Hi @tenzen-y 👋, 1.33 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 5th March, 2025. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 2025: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[tenzen-y]

Hi @tenzen-y 👋, 1.33 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 5th March, 2025. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 2025: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

Thank you for reminding me! I would like to write a blog about this feature since we did not write a blog about this in every feature stage. I will open a placeholder PR until the deadline. Thanks!

[tenzen-y]

Hey again @tenzen-y 👋, v1.33 Enhancements team here,

Just checking in as we approach Code Freeze at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).[ ] All PRs are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, I couldn’t find any PR listed in the GitHub issue, neither can I find any associated PRs in kubernetes/kubernetes--could you please share the list of PRs that need tracking?

1. Please list the PRs that need to be merged before code freeze
2. Please Update the Issue description to include all the related PRs of this KEP

If you anticipate missing code freeze, you can file an exception request in advance. Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

The status of this enhancement is marked as At risk for code freeze.

As always, we are here to help if any questions come up. Thanks!

Thank you for reminding me. I opened k/k PR and add the link to this issue, thanks.

[dipesh-rawat]

Hi @tenzen-y 👋, v1.33 Enhancements team here,

Just a quick friendly reminder as we approach the code freeze later this week, at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

The current status of this enhancement is marked as At risk for code freeze. There are a few requirements mentioned in the comment #3998 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

[tenzen-y]

Hi @tenzen-y 👋, v1.33 Enhancements team here,

Just a quick friendly reminder as we approach the code freeze later this week, at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

The current status of this enhancement is marked as At risk for code freeze. There are a few requirements mentioned in the comment #3998 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

HI, @dipesh-rawat Thank you for contacting me. All PRs are merged right now.

[fykaa]

Hi @tenzen-y, thanks for the update! I'll double-check the status and update the tracking accordingly.

also, please let me know if anything changes before the freeze and/or there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status.