Job API managed-by mechanism about enhancements HOT 14 OPEN

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

from enhancements.

@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

from enhancements.

/sig apps
/wg batch
/assign

from enhancements.

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!

from enhancements.

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 🚀

from enhancements.