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 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! 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 |
Thanks, @Priyankasaggu11929 |
Hey @pacoxu, thanks for the prompt update. The Open PR still misses updating the Could you please update the PR with the same. Thank you so much! |
Updated in 45a80c4. Thanks. |
With KEP PR #2697 merged, the enhancement is ready for the 1.25 Enhancements Freeze. For note, the status is now marked as |
Hello @pacoxu! 1.25 Release Docs Shadow here. Does this enhancement work planned for 1.25 require any new docs or modification to existing docs? If so, please make sure to open a PR against the This PR can be just a placeholder at this time and must be created before August 4. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. |
Hi @pacoxu Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022. Please ensure the following items are completed:
Please verify, if there are any additional k/k PRs besides the ones listed above. Please plan to get the open k/k merged by the code freeze deadline. The status of the enhancement is currently marked as Please also update the issue description with the relevant links for tracking purpose. Thank you so much! |
@Priyankasaggu11929 Thanks for reminding me. |
The PRs were merged. I will open a website update pr later. |
Thank you so much for the update, @pacoxu. With the PRs merged, the enhancement is ready for 1.25 code freeze. The status is now marked as |
Openshift team meet a bug with this feature after we enable it by default in kubernetes/kubernetes#112076. And @rphillips raise a pr to revert this feature to alpha. |
@pacoxu Please update the enhancement as it still shows it as being beta in 1.25: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/1029-ephemeral-storage-quotas/kep.yaml cc: @sftim |
This feature has been reverted to alpha in master and 1.25. Related-to: kubernetes/kubernetes#112076 Related-to: kubernetes/kubernetes#112078 Related-to: kubernetes/enhancements#1029
This feature has been reverted to alpha in master and 1.25. Related-to: kubernetes/kubernetes#112076 Related-to: kubernetes/kubernetes#112078 Related-to: kubernetes/enhancements#1029
I have tried to promote it to beta in v1.25 and openshift found a regression issue on it. Currently, v1.25.1 and v1.26 will revert it to alpha. Only this feature is in beta only in v1.25.0. |
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? |
Enhancement Description
The text was updated successfully, but these errors were encountered: