-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move cgroup v1 support into maintenance mode #4569
Comments
/sig node |
/assign |
I updated the name of a KEP (this issue title) as per our decision: #4572 (comment). @harche can you please update it in kep.yaml as well? |
/label lead-opted-in |
Hello @harche 👋, 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 Here’s where this enhancement currently stands:
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 |
/stage alpha |
@sreeram-venkitesh this feature is going straight for GA. There is no alpha or beta stage for this feature. |
@harche Thanks for clarifying! Would you consider this KEP as of type /stage stable |
This KEP is not going to deprecate cgroup v1 support, hence we would not like to classify it as |
Thanks for the quick update! |
Hello @harche 👋, 1.31 Docs Shadow here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you! |
|
Hi @harche, 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! 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 |
Hey @harche, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog. |
@rashansmith thanks for reaching out. I have created a placeholder PR for the blog post - kubernetes/website#47069 |
@harche Hi there 👋 I'm Abbie the release comms lead. Just wanted to double check, should this KEP be included in our deprecations and removals blog for 1.31? I see that we aren't classifying this as a deprecation, but do you think its worth highlight to users in the same way? thanks! |
Hi @harche - 👋 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:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:
If you anticipate missing code freeze, you can file an exception request in advance. Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
@harche could you add kubernetes/kubernetes#126031 to the issue description? |
Done, thanks. |
/stage alpha |
@harche @kannon92 Looks like all the PRs linked in #4569 (comment) are merged. Are we good for code freeze? Are there any other PRs that needs to be merged for this KEP? Thanks! |
@kannon92 this is going straight for stable. |
All the PRs in kubernetes/kubernetes are merged, the documentation PRs (kubernetes/website) are still getting reviewed. |
Oh. Can you update the description then? I see that they are added to alpha so I figured it was a mistake to have it labeled as stable. |
Updated, thanks. |
Thanks @harche! Marking this KEP as |
/stage stable |
Hello 👋 1.32 Enhancements Lead here, I'm closing milestone 1.31 now, /milestone clear |
Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32. /remove-label lead-opted-in |
Enhancement Description
k/enhancements
) update PR(s): Move cgroup v1 support into maintenance mode #4572k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: