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
Quotas for Ephemeral Storage #1029
Comments
/sig node |
per sig-node discussion, this is good. the kep will merge here: #646 /milestone v1.15 |
@RobertKrawitz This is OK to track for 1.15. However, please update the KEP with established graduation criteria for Beta and Alpha when possible. /stage alpha |
Hey, @RobertKrawitz @derekwaynecarr 👋 I'm the v1.15 docs Lead. Just a friendly reminder we're looking for a PR against k/website (branch dev-1.15) due by Thursday, May 30th. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions! |
Yes, this will require new documentation. I will open the website PR today. |
Hi @RobertKrawitz @derekwaynecarr . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open. Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone. If you know this will slip, please reply back and let us know. Thanks! |
Hey, @RobertKrawitz @derekwaynecarr .Just a friendly reminder we're looking for at least a draft/placeholder PR against k/website (branch dev-1.15) due by Thursday, May 30th 2019 @ EOD PST. |
@makoscafee The k/website PR is kubernetes/website#14268 |
Hi @RobertKrawitz @derekwaynecarr , today is code freeze. I do not see a reply for any k/k PRs to track for this merge. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. If there is no response, or you respond with PRs to track and they are not merged by EOD PST, this will be dropped from the 1.15 Milestone. After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception. |
The PR for this is kubernetes/kubernetes#66928 |
/hold cancel |
Hi @RobertKrawitz , I'm the 1.16 Enhancement Lead. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.6 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label. Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly. Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29. Thank you. |
Hello @RobertKrawitz -- 1.17 Enhancement Shadow here! 🙂 I wanted to reach out to see if this enhancement will be graduating to alpha/beta/stable in 1.17?
Thank you! 🔔Friendly Reminder The current release schedule is
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
If kubernetes/kubernetes#112624 can fix the bug we meet in v1.25.0, can we re-promote this feature to beta? |
There are some discussions about this feature in the last sig node meetings.
I prefer to promote this feature if the blocking bugs(kubernetes/kubernetes#112081) are fixed. The reason is that du in some scenarios will hang or take too much time. It happens in our customers' clusters and we want to alter it to a stable quick way for that. This is one of the solutions. Of course, there may be some other ways.
This is one of the reasons that @rphillips asked for deprecating this feature as it is not promoted to beta for a long time. Should we open an issue to track this security problem? |
https://testgrid.k8s.io/sig-node-kubelet#kubelet-gce-e2e-fsquota-ubuntu is added for this feature to enable it in tests. |
/milestone v1.28 adding tracking of this feature since it is being worked on |
|
/label lead-opted-in |
Hello @pacoxu 👋, 1.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:
It looks like https://github.com/kubernetes/enhancements/pull/3821/files will address most of these issues. The status of this enhancement is marked as |
Hi @pacoxu, just checking in once more as we approach the 1.29 enhancement freeze deadline this week on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as It looks like when #3821 merges in it will address most of the requirements. Let me know if I missed anything. Thanks! |
With #3821 merged this is now |
Hello @RobertKrawitz @pacoxu 👋, v1.29 Docs Shadow here. |
kubernetes/website#43455 is open for website. |
Hi @pacoxu, 👋 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. |
Hey again @pacoxu 👋 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:
For this enhancement, it looks like the following PRs have been merged:
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): The status of this KEP is currently Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
The pr needs review/approve. |
Hello @pacoxu 👋 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 |
Enhancement Description
k/enhancements
) update PR(s): Updates from SIG-Node meeting 20181204 #646k/k
) update PR(s): Ephemeral storage monitoring via filesystem quotas kubernetes#66928k/website
) update(s): Add support for quotas for ephemeral storage monitoring. website#14268k/enhancements
) update PR(s): promote ephemeral-storage-quotas to beta in 1.25 #2697k/k
) update PR(s):k/website
) updates: Revert: promote LocalStorageCapacityIsolationFSQuotaMonitoring to beta website#36401k/enhancements
) update PR(s): [v1.29] ephemeral-storage-quotas: repromote to beta #3821k/k
) update PR(s):k/website
) update(s): [WIP] Update LocalStorageCapacityIsolationFSQuotaMonitoring to beta website#43455The text was updated successfully, but these errors were encountered: