-
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
Prioritizing nodes based on volume capacity #1845
Comments
/sig storage |
/assign |
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. |
/lifecycle fronzen |
/remove-lifecycle stale |
yes |
Thanks! @kubernetes/sig-release can we track this? |
Done! |
Enhancements Lead here, there is no alpha graduation criteria, can you please add as it's not clear what will be delivered? Also can you please clarify in the test plans whether you intend to implement all of those for alpha? or will some come later? The graduation criteria listed for all phases seems rather vague as well, if you could provide more detail please do. Note : Enhancements Freeze is October 6th and by that time all KEPs must have test plans & graduation criteria. |
Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates: As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them. Thanks! |
Hello @cofyc 👋, 1.20 Docs shadow here. Does this enhancement work planned for 1.20 require any new docs or modification to existing docs? This PR can be just a placeholder at this time and must be created before Nov 6th Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Thanks! |
Hey @cofyc 👋 The docs placeholder deadline is almost here. Please make sure to create a placeholder PR against the Also, please keep in mind the important upcoming dates:
As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track. Thanks ! |
@msau42 @xing-yang can you move this KEP to the 1.21 milestone? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
The Kubernetes project currently lacks enough active 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 rotten |
/remove-lifecycle rotten |
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 |
The Kubernetes project currently lacks enough active 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 rotten |
/remove-lifecycle rotten |
/lifecycle frozen |
/milestone clear |
I don't yet see any documentation (the feature gate is listed as being available). Is https://kubernetes.io/docs/concepts/storage/storage-capacity/ the right place to add it? |
Enhancement Description
Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
ref: kubernetes/kubernetes#83323
ref: volume topology scheduling design proposal
The text was updated successfully, but these errors were encountered: