-
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
Support PSI based on cgroupv2 #4205
Comments
/sig node |
/milestone v1.29 @ndixita please fill up more details in the issue description. Accepting as we discussed at SIG Node meeting this week |
/cc |
Hello @ndixita 👋, v1.29 Enhancements team here. Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
Hi @ndixita 👋🏽 checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as |
The KEP PR is updated, and the comments are resolved. I am waiting for PRR review |
With KEP PR #4230 approved, the enhancement is ready for the enhancements freeze. The status is now marked as |
Hey there @ndixita! 👋, v1.29 Docs Lead here. |
Hi again @ndixita! The deadline to open a placeholder PR against k/website for required documentation is this Thursday, 19 October. Could you please update me on the status of docs for this enhancement? Thank you! |
Hey again @ndixita 👋, 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:
Please update the Issue description to include all the related PRs of this KEP under the 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 @ndixita, 👋 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. |
@a-mccarthy This feature is postponed to 1.30 release |
Hello @ndixita 👋 1.29 Enhancements lead 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 1.29 milestone. If you still wish to progress this enhancement in 1.29, please file an exception request. Thanks! /milestone clear |
This would be quite useful to have as we can use the psi metrics as a good proxy for memory pressure and potential for OOMKILL. Thanks |
/remove-label lead-opted-in |
/stage alpha |
Hello @ndixita 👋, 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 stage Here's where this enhancement currently stands:
For this KEP, it looks like we just need to do the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
/milestone 1.32 |
@ndixita: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Hi @ndixita! Are we deferring this KEP for the next release? |
Yes, since the runc dependency is not in yet. Please defer this KEP to next release. |
/milestone clear |
/label tracked/no |
Some update from cadvisor\runc\containerd:
|
Waiting for runc 1.2.0. https://github.com/opencontainers/runc/milestone/13 |
@mrunalp has mentioned that runc 1.2 could happen so I'm going to propose this for 1.32. |
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 |
@tjons I would like to get this added to 1.32. Could you please help me get this KEP added? |
/milestone v1.32 |
Hello @ndixita 👋, v1.32 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
I've opened a PR for this in #4883 |
done, thanks @kannon92 ! |
Hello @ndixita 👋, v1.32 Enhancements team here, Now that PR #4883 has been merged, all the KEP requirements are in place and merged into k/enhancements. The status of this enhancement is now marked as |
Enhancement Description
k/enhancements
) update PR(s):k/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: