Job API managed-by mechanism

[mimowo]

Enhancement Description

• One-line enhancement description: Support managed-by mechanism for Jobs

• Kubernetes Enhancement Proposal: KEP-4368: Support managedBy field for Jobs

• Discussion Link: Job API proposal for MultiKueue, and sig-apps meeting Nov 27,2023, and wg-batch meeting Jan 18 2024

• Primary contact (assignee): @mimowo

• Responsible SIGs: apps

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): 1.30
  • Beta release target (x.y): 1.32
  • Stable release target (x.y):

• Alpha

  • KEP (k/enhancements) update PR(s):
    • KEP-4368: Job API managed-by label #4370
    • KEP-4368 update to use managedBy field instead of label #4530
  • Code (k/k) update PR(s):
    • Support for the Job managedBy field (alpha) kubernetes#123273
    • Update Job conformance test for job status updates kubernetes#123751
    • Follow up fix to the job status update test kubernetes#123815
    • Adjust the Job field API comments and validation to the current state kubernetes#123792
    • Fix the comment for the Job managedBy field kubernetes#124793
  • Docs (k/website) update(s):
    • Add docs for Job managedBy field (alpha) website#45132

• Second Alpha (1.31)

  • KEP (k/enhancements) update PR(s):
    • Update the managedBy KEP with fix for terminating pods #4657
  • Code (k/k) update PR(s):
    • Count terminating pods when deleting active pods for failed jobs kubernetes#125175
    • Delay setting terminal Job conditions until all pods are terminal kubernetes#125510
    • Update the count of ready pods when deleting pods kubernetes#125546
  • Docs (k/website) update(s):
    • Update the docs for JobManagedBy and JobPodReplacementPolicy related to pod termination website#46808

• Beta

  • KEP (k/enhancements) update PR(s):
    • Update "KEP-4368 Job API managed-by mechanism" targeting Beta in 1.32 #4856
  • Code (k/k) update PR(s):
    • Graduate JobManagedBy to Beta in 1.32 kubernetes#127402
  • Docs (k/website) update(s):
    • Update docs as JobManagedBy graduates to Beta website#48378

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

[mimowo]

/sig apps
/wg batch
/assign

[soltysh]

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

[mickeyboxell]

Hello @mimowo 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on [02:00 UTC Friday 9th February 2024 / 18:00 PDT Thursday 8th February 2024](https://everytimezone.com/s/1ade3dca):.

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

Here's where this enhancement currently stands:

• KEP readme using the [latest template](https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template) has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.30. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• 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](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#submitting-a-kep-for-production-readiness-approval)).

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

• KEP status is marked as implementable for latest-milestone: 1.30.

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!

[mimowo]

@mickeyboxell would you like to take a look at why the checkbox about status: implementable and latest-milestone: 1.30 isn't checked? It seems the fields are filled accordingly in kep.yaml

[mickeyboxell]

Thanks for catching that. It looks like an oversight on my part.

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

[sftim]

BTW, the issue description should link to https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/4368-support-managed-by-label-for-batch-jobs (instead of to #4370)

[celestehorgan]

@mimowo Can you open a placeholder docs PR for this by Thursday? Thank you 🙏

[mimowo]

@mimowo Can you open a placeholder docs PR for this by Thursday? Thank you 🙏

Sure, PTAL: kubernetes/website#45132.

[natalisucks]

Hi @mimowo,

👋 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

[mickeyboxell]

Hey again @mimowo 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

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 PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• Support for the Job managedBy field (alpha) kubernetes#123273

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

[dipesh-rawat]

Can you point me where I should "readd it

@mimowo To opt in an enhancement, the SIG lead needs to add the 'lead-opted-in' label and set the milestone to v1.32 before the Production Readiness Review Freeze.

Refer to the instructions here in the v1.32 Call for Enhancements announcement.

[soltysh]

/label lead-opted-in
/milestone v1.32
/stage beta

[jenshu]

Hello @mimowo 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage beta for v1.32 (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: v1.32.
• 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 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

• In your kep.yaml, the latest-milestone needs to be updated to v1.32

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.

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

[mimowo]

@jenshu the latest-milestone is bumped after #4881. PTAL.

[jenshu]

@mimowo thanks! Everything looks good, I have updated the issue status to tracked for enhancements freeze

[rdalbuquerque]

Hello @mimowo 👋, 1.32 Docs Shadow here.
Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 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!

[mimowo]

@rdalbuquerque sure, opened the PR: kubernetes/website#48378

[rytswd]

Hi @mimowo 👋 -- this is Ryota (@rytswd) from the v1.32 Communications Team!

For the v1.32 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, 30th Oct 2024? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: 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.

[jenshu]

Hello @mimowo 👋, v1.32 Enhancements team here.

With all the implementation (code related) PRs merged per the issue description:

• Graduate JobManagedBy to Beta in 1.32 kubernetes#127402

This enhancement is now marked as tracked for code freeze for the v1.32 Code Freeze!

Additionally, please let me know if there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status.

[rytswd]

Hi @mimowo 👋, v1.32 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 30th Oct. 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!

[dipesh-rawat]

Hello 👋, 1.33 Enhancements Lead here.

I’m closing milestone 1.32 now. If you'd like to work on this enhancement in v1.33, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.33 using /milestone v1.33.
Thanks!

/remove-label lead-opted-in
/milestone clear

[mimowo]

The plan is to incubate the feature in Beta for at least 2 releases, so we aren't aiming for graduation in 1.33.