/sig apps
/wg batch
/assign

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

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!

@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

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 🚀

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)

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

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

Sure, PTAL: kubernetes/website#45132.

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

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!

/stage alpha

Hi @mimowo 👋 Enhancements team here, just a friendly reminder to follow up on the open Enhancement items above prior to code freeze at 02:00 UTC Wednesday 6th March 2024.

Hey again @mimowo 👋 Enhancements team here,

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

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

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

The last thing to do is to update the status field in the kep.yaml file to implemented when the code PRs are merged and the feature gates are removed.

@mickeyboxell could you please update the speadsheet to indicate this is Alpha stage: https://github.com/orgs/kubernetes/projects/175/views/1?filterQuery=managed?