Hello @jpbetz and @liggitt 👋, 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 stable 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).

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, I couldn't find any related PR regarding this KEP in k/enhancements. Thank you!

Hello @jpbetz and @liggitt 👋, 1.30 Docs Lead here.

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!

Hi @thockin

👋 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

Very excited to see this. Thank you!

I'd like to draw a little bit of attention to a related issue: kubernetes/apiextensions-apiserver#57. Perhaps it'll become easier to address once it's easier to have modules thanks to using workspaces.

I don't think this needs user-facing docs, but a blog post seems possible. I am sort of AFK this week but will look at what I can do.

Hi @thockin,

Thank you for opting in for a 1.30 Feature Blog -- I know you are out this week, but can you open a placeholder PR by February 26th?

Hey again @jpbetz, @liggitt, and @thockin 👋 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):

• Go workspaces for k/k and staging kubernetes#122624

With this, it is now marked as at risk for code freeze for the v1.30 Code Freeze!

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!

The main gengo change has landed (kubernetes/gengo#259).

A small followup is needed (kubernetes/gengo#261) and then kube-openapi can land (kubernetes/kube-openapi#457). After that I will rebase kubernetes/kubernetes#122624 for k/k.

kubernetes/kube-openapi#458 is pending now.

@thockin

Hello! This is a friendly reminder that the placeholder PR is due on Feb 27 (tomorrow as of the time of writing this comment).

To opt in, you need to open a Feature Blog placeholder PR against the website repository.
Here's the 1.30 Release Calendar

Cheers,
Frederick

kubernetes/website#45358

Merged!

With this being merged, this enhancement can be marked as tracked.