/sig api-machinery

/milestone v1.28
/label lead-opted-in

/stage alpha

Hello @alexzielenski 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023.

This enhancement is targeting for stage alpha for v1.28 (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.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following:
-Fill out questions on e2e test,Rollout, Upgrade and Rollback Planning, monitoring requirements.
-Ensure the Pr is merged

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

Thanks @alexzielenski :)
With all the KEP requirements 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. Please keep the issue description up-to-date with appropriate stages as well.

Hello @alexzielenski! 1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Thanks @katcosgrove I've created the placeholder PR and edited the description.

This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Hopefully I am in time. I'm assuming that since you posted on Wed Jul 21, you meant Thu Jul 22, instead of 20.

Hey @alexzielenski Enhancements team here 👋

Just checking in as we approach Code freeze at 01:00 UTC Wednesday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

• All the PRs that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
• All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.

I don't see any code (k/k) update PR(s) in the issue description so if there are any k/k related PR(s) that we should be tracking for this KEP please link them in the issue description above.

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

Just confirming that code for this feature has merged: kubernetes/kubernetes#118990 (and it included in the description for tracking purposes)

Hey @alexzielenski 👋 Enhancements Lead here,
With kubernetes/kubernetes#118990 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze! Thanks :)

Hello @alexzielenski wave: please take a look at Documenting for a release - PR Ready for Review to get your docs PR ready for review before Tuesday 25th July 2023. Thank you!

Ref: kubernetes/website#41737

/remove-label lead-opted-in

Hi @alexzielenski, is this KEP targeting 1.29? If it is, can you make sure the lead-opted-in label is set on the issue so it is correctly tracked by the enhancements project board? Thanks!

BTW, the issue description (still) reads: “Draft KEP for upcoming SIG API Machinery proposal”

/label lead-opted-in

Hello @alexzielenski 👋, 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:

• I see that there is an open PR KEP-4008: Promote CRD Ratcheting to GA #5082 containing all of the above updates. This will need to be merged prior to enhancements freeze

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!

Hello @alexzielenski 👋, 1.33 Enhancements team here,

Now that PR #5082 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 and have the KEP issue assigned to someone. Thank you!

/label tracked/yes

As a reminder, please have this KEP issue assigned to someone prior to enhancements freeze. Currently, there is no assignee for this issue. Thank you!

Hello, @alexzielenski 👋, v1.33 Docs Shadow here.

Does this enhancement work planned for v1.33 require any new docs or modifications to existing docs?

If so, please follow the steps here to open a PR against the 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 familiarized with the docs requirement for the release.

Thank you!

Hi @alexzielenski 👋 v1.33 Docs Lead here.

Gentle reminder! The deadline to raise a placeholder Docs PR is Thursday 27th February 2025 18:00 PDT.
If this enhancement work requires any new docs or modification to existing docs, please create a placeholder PR (it can be a draft PR for now) before the deadline.

Thanks!

Hi @rayandas , here is the placeholder Docs PR kubernetes/website#49921

Thanks @yongruilin

Hi @alexzielenski 👋 -- this is Aakanksha (@aakankshabhende ) 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 📚

Hey again @alexzielenski 👋, 1.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 KEP, we would need to do the following:

• Ensure all PRs to the Kubernetes repo related to your enhancement are linked in the above issue description (for tracking purposes).
• Ensure all PRs are prepared for merging (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

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

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

Hi @alexzielenski 👋 -- this is Aakanksha (@aakankshabhende ) from 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!

CC: @yongruilin for the comms and code freeze updates. You're driving the GA graduation for this KEP right?

CC: @yongruilin for the comms and code freeze updates. You're driving the GA graduation for this KEP right?

Yes, I will finish up the GA graduation for this.

Hi @yongruilin @alexzielenski 👋, 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 #4008 (comment) that still need to be completed.

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

@dipesh-rawat
The code k/k PR is kubernetes/kubernetes#130013 merged
The doc PR has placeholder kubernetes/website#49921, should this subject to doc freeze instead of code freeze?

@yongruilin Thanks for the update on the PR kubernetes/kubernetes#130013! Could we also link the PR in the issue description (here)? Also, can you confirm if there are any other code or test PRs planned for this v1.33 release before we update the KEP status on the board for code freeze.

Regarding the documentation PR, it should be merged by the docs freeze deadline (Tuesday 8th April 2025), which comes later than the code freeze.

Additionally, can we please ensure this issue is assigned to someone.

/assign
But I don't have permission to update it.

Also, can you confirm if there are any other code or test PRs planned for this v1.33 release before we update the KEP status on the board for code freeze.

No other code/test PRs planned for v1.33 besides kubernetes/kubernetes#130013

I have permission. Docs placeholder link added.

Lack of edit access to KEP issues due to change of primary contributor has become more common.

@yongruilin Thanks, for the update and confirming that all required changes are merged. I’ll mark this as tracked for code freeze and add the mention of kubernetes/kubernetes#130013 in the issue description. Also, please let us know if anything changes before the freeze or if there are any other PRs in k/k we should track for this KEP to keep the status accurate.

This enhancement is now marked as tracked for code freeze for the 1.33 Code Freeze!