/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

Hi @taniaduggal! Sorry for the delay, I've created the placeholder and updated and description with its link

Hey again @alexzielenski 👋 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November.

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:

• KEP-4008: CRDValidationRatcheting: Ratchet errors from CEL expressions if old DeepEqual new kubernetes#121016
• KEP-4008: CRDValidationRatcheting: Add support for optional oldSelf kubernetes#121034
• KEP-4008: CRDValidationRatcheting: Add Benchmarks kubernetes#121405

With all this, the status of this KEP is at risk for 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!

Hi @alexzielenski, 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository.
The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here is the 1.29 calendar

Hi @alexzielenski, 1.29 Enhancement lead here. This KEP is currently at risk for code freeze. We have received your exception request and are reviewing it. Thanks!

This is deffering to 1.30 as per: https://kubernetes.slack.com/archives/C2C40FMNF/p1698797744244589

We will keep this as tracked for code freeze for Alpha 2 on the enhancements tracking board as this will require docs changes for 1.29 since new fields have been added already in 1.29 to CRDs for this feature.

Hyy @alexzielenski , Just a reminder that the deadline for docs merge is Tuesday (November 28).

/remove-label lead-opted-in

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.29 now,
If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

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

@jpbetz @alexzielenski looks like this was opted in and there is a k/k PR to bump to beta, this was PRR approved for 1.29 and didn't make it and was deferred correct?

Hello @alexzielenski 👋, 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 beta for 1.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. 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).

For this KEP, we would just need to update the following:
- Updated latest-milestone to v1.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!

@jeremyrickard thats correct we meant to upgrade this feature to beta in 1.29, but deferred doing so since an API change was made.

@jeremyrickard thats correct we meant to upgrade this feature to beta in 1.29, but deferred doing so since an API change was made.

Here's the 1.30 KEP update, it looks like GitHub didn't figure out how to link it here due to the indirect link - this needs SIG API machinery approval, but not PRR (which it already has): #4490

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

Hi @alexzielenski,

👋 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

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

Does this enhancement work planned for v1.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!

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

At a minimum, we'll need a docs PR upgrading the stability version of CRDValidationRatcheting feature gate. Marking as Need Docs. Thanks!

Opened placeholder PR here: kubernetes/website#45264

Also opened placeholder for feature blog post: kubernetes/website#45265

Also opened placeholder for feature blog post: kubernetes/website#45265

@alexzielenski I may be missing something, but the placeholder should only be one file (the actual blog post template), whereas I am seeing 11 changed files in your PR. Let me know if there's anything we can assist with.

Hello @alexzielenski 👋, Enhancements team here.

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

• KEP-4008: CRDValidationRatcheting Bump Feature Gate To Beta kubernetes#121461

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