Enhancements: Prioritizing nodes based on volume capacity

[cofyc]

Enhancement Description

• One-line enhancement description (can be used as a release note): Prioritizing nodes based on volume capacity
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1845-prioritization-on-volume-capacity
• Primary contact (assignee):@cofyc
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y) 1.20
  
  
  • Beta release target (x.y) 1.21
  
  
  • Stable release target (x.y) 1.22
  
  

_Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement_

ref: https://github.com/kubernetes/kubernetes/issues/83323
ref: volume topology scheduling design proposal

[cofyc]

/sig storage
/sig scheduling

[cofyc]

/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cofyc]

/lifecycle fronzen

[msau42]

/remove-lifecycle stale
@cofyc do you plan to target an implementation in 1.20?

[cofyc]

/remove-lifecycle stale

@cofyc do you plan to target an implementation in 1.20?

yes

[msau42]

Thanks!

@kubernetes/sig-release can we track this?

[kikisdeliveryservice]

Thanks!

@kubernetes/sig-release can we track this?

Done!

[kikisdeliveryservice]

Hi @msau42 @cofyc

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.

[kikisdeliveryservice]

Hi @cofyc @msau42

Thanks for the PR! It clearly updates the graduation criteria! As a reminder it will need to merge by October 6th

Thanks
Kirsten

Update: it merged!!! yay!

[kikisdeliveryservice]

Hey there Hi @cofyc @msau42 :wave:

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

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!
Kirsten

[eagleusb]

Hello @cofyc :wave:, 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo.

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!

[cofyc]

Hello @cofyc 👋, 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo.

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!

[eagleusb]

Hey @cofyc :wave:

The docs placeholder deadline is almost here.

Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline.

Also, please keep in mind the important upcoming dates:

• Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review

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 !

[cofyc]

@eagleusb PTAL https://github.com/kubernetes/website/pull/24858

[cofyc]

@msau42 @xing-yang can you move this KEP to the 1.21 milestone?
I've submitted a PR: https://github.com/kubernetes/kubernetes/pull/96347 but may not finish the tests before the code freeze.

[xing-yang]

Sure.