/sig api-machinery

@jpbetz please provide a Discussion Link. It is required that you "link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation" :)

/lead-opted-in

/milestone v1.26

/lead-opted-in

/sig api-machinery

/label tracked/yes

Hello @jpbetz 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (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.26
• 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 before enhancements freeze which is approaching soon:

• update the status of the KEP in the kep.yaml to implemetable.
• check the agreement in the test plan section and add graduation criteria for alpha phase(if need being).
• Complete and merge the PRR for the kep

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!

#3554 contains PRR, test, graduation and implementable, we are aiming to merge it today

@parul5sahoo Thanks for reaching out! We have everything merged. The KEP can be tracked now. Please let us know of anything is missing :)

Hello @cici37 , although I see that the release sign off checklist and the test agreement have been included but they are all unchecked. so could you please check the items that meet the criteria in the release check list and also the check the test agreement. And since these are minor details I am marking the KEP as tracked.

Hello @cici37 , although I see that the release sign off checklist and the test agreement have been included but they are all unchecked. so could you please check the items that meet the criteria in the release check list and also the check the test agreement. And since these are minor details I am marking the KEP as tracked.

#3592 to address this. Thanks for marking this tracked!

/assign

@cici37 Please try to get it merged before the enhancements freeze. Thanks.

@rayandas It is merged. Thanks!

As #4272 is now merged, marking this as Tracked for Enhancements Freeze. 🚀 Thanks.

Hey there @jpbetz ! 👋, v1.29 Docs team shadow here.
Does this enhancement work planned for v1.29 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release.
Thank you!

^ @cici37

We might not need a doc PR for this release. We'll raise one later if the doc update is needed.

Hey again @jpbetz 👋, 1.29 Enhancements team here,

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

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.

Please update the Issue description to include all the related PRs of this KEP under the beta section in the Github Issue description. The status for this KEP is currently 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 @jpbetz, 👋 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 @jpbetz , 👋 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.

Not for this release. We're letting this feature settle in as a Beta feature with only relatively minor improvements.

@cici37 please feel free to disagree if you'd like to publish anything.

Hey again @cici37 @jpbetz 👋, 1.29 Enhancements team here! Are there any code PRs going into 1.29 we should track as part of this KEP? Or could you confirm that there are no net new code changes in 1.29?

Confirmed that 1.29 code changes had mainly bug fixes, marking this as tracked for code freeze 🚀

Is this targeting stable in 1.30?

/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

Yes we plan to promote this to GA in 1.30.

/milestone v1.30

@jpbetz Could you please tag the leader opt in label here? Thanks!

/lead opt-in

/label lead-opted-in

Hello @cici37, @jpbetz 👋, v1.30 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. 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).

The status of this enhancement is marked as tracked for enhancement freeze 🎉 Thank you!

Hello @jpbetz , 👋 1.30 Docs Shadow here.
Does this enhancement work planned for 1.30 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against the 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 @jpbetz, @cici37,

👋 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

Hi @jpbetz, @cici37

👋 from the v1.30 Communications Team!

We are currently working on the midcycle blog. We are looking for a paragraph or two about significant enhancements. Are you interested in participating?

Here's the link for general access (commenter permissions). We can extend editor permissions if you choose to author an entry in this blog post.

Also, please get in touch with us if there are other changes you believe could impact users that we should highlight. We can be reached at #release-comms in the Kubernetes Slack.

Cheers,
Frederick

Hey again @jpbetz, @cici37 👋 v1.30 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):

• [KEP-3488]Promote ValidatingAdmissionPolicy to GA kubernetes#123405

Currently, I'm marking this KEP as 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!

@cici37, @jpbetz Please let me know if kubernetes/kubernetes#123405 is the only code PR that needs to be merged for this KEP. Pinging again since code freeze is tomorrow.

Please let me know if kubernetes/kubernetes#123405 is the only code PR that needs to be merged for this KEP. Pinging again since code freeze is tomorrow.

We're also merging kubernetes/kubernetes#123543. It's in the merge queue now. I've added it to the description for tracking. kubernetes/kubernetes#123405 is ready and will be merged after.

Thank you @jpbetz, @cici37!

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

• ValidatingAdmissionPolicy: exclude brink-able resources. kubernetes#123543
• [KEP-3488]Promote ValidatingAdmissionPolicy to GA kubernetes#123405

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