Closed mortent closed 1 month ago
Hey again @atiratree and @ravisantoshgudimetla 👋 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:
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):
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!
Hello @atiratree and @ravisantoshgudimetla 👋 Enhancements team here,
Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.30
milestone.
If you still wish to progress this enhancement in v1.30
, please file an exception request. Thanks!
/milestone clear
Hi 👋, 1.31 Enhancements Lead here.
If you wish to progress this enhancement in v1.31, please have the SIG lead opt-in your enhancement by adding the lead-opted-in label and set the milestone to v1.31 before the Production Readiness Review Freeze.
/remove-label lead-opted-in
I plan to graduate this feature to GA in 1.31:
KEP update: https://github.com/kubernetes/enhancements/pull/4669
/label lead-opted-in /milestone v1.31
Hello @atiratree 👋, v1.31 Enhancements team here.
Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.
This enhancement is targeting for stage stable
for v1.31 (correct me, if otherwise)
Here's where this enhancement currently stands:
implementable
for latest-milestone: v1.31
. KEPs targeting stable
will need to be marked as implemented
after code PRs are merged and the feature gates are removed.For this KEP, https://github.com/kubernetes/enhancements/pull/4669 takes care of all the changes required. Please make sure that it is merged in time before the enhancements freeze!
The status of this enhancement is marked as At risk for enhancements freeze
. Once the above PR is merged, I can mark it as tracked.
If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!
With #4669 merged, we can mark this KEP as tracked for enhancements freeze 🎉
Hello @atiratree 👋, 1.31 Docs Shadow here.
Does the work related to this KEP planned for 1.31 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.
Thank you!
Hello, @atiratree and @ravisantoshgudimetla!
👋 from the v1.31 Communications Team!
We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.
To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.
Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.
@salaxander opened a placeholder PR for the docs https://github.com/kubernetes/website/pull/45263
Hey again @atiratree 👋 v1.31 Enhancements team here,
Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024 .
Here's where this enhancement currently stands:
approved
and lgtm
labels applied) by the code freeze deadline. This includes tests.List of associated PRs:
If you anticipate missing code freeze, you can file an exception request in advance.
This KEP is marked as Tracked for code freeze
. Thanks a lot for keeping the issue description up to date! 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!
Closing this as it was implemented in the 1.31 release. Thanks all!
Enhancement Description
PodHealthyPolicy
to PodDisruptionBudgetk/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):k/enhancements
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.