Add storage capacity scoring

[cupnes]

Enhancement Description

• One-line enhancement description (can be used as a release note): Storage Capacity Scoring of Nodes for Dynamic Provisioning
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/4049-storage-capacity-scoring-of-nodes-for-dynamic-provisioning/README.md
• Discussion Link:
  • ML(sig-storage): https://groups.google.com/g/kubernetes-sig-storage/c/RQHvFvG6pPY/m/wFoLU61bAwAJ
  • Slack(#sig-storage): https://kubernetes.slack.com/archives/C09QZFCE5/p1685002022790859
• Primary contact (assignee): @cupnes
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4049: Add storage capacity scoring KEP #4042
  • Code (k/k) update PR(s): KEP-4049: Add storage capacity scoring to VolumeBinding plugin kubernetes#128184
  • Docs (k/website) update PR(s): KEP-4049: Add StorageCapacityScoring feature gate documents website#48382

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

[cupnes]

/sig storage

[xing-yang]

Confirmed with @cupnes that this feature is not targeting alpha in 1.28.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[cupnes]

The is under review at #4042.
/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[cupnes]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[xing-yang]

/remove-lifecycle stale

[xing-yang]

/milestone v1.32

[cupnes]

@rashansmith
I created placeholder PR for blog.
kubernetes/website#48416

[dipesh-rawat]

Hey again @cupnes 👋 v1.32 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like 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):

• KEP-4049: Add storage capacity scoring to VolumeBinding plugin kubernetes#128184

Additionally, please let me know if there are any other PRs in k/k not listed in the description or linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status.

The status of this enhancement is marked as at risk for code freeze.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

[cupnes]

@dipesh-rawat
Thank you for your message. I updated this issue's description.

[dipesh-rawat]

Hey again @cupnes 👋, v1.32 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in few days, at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment #4049 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance.

[cupnes]

@xing-yang @dipesh-rawat
The following PR to k/k for this KEP will not be ready by the code freeze. Therefore, please skip the alpha for this KEP at version 1.32.
kubernetes/kubernetes#128184

[cupnes]

@rdalbuquerque
As mentioned in the above comment, the PR to k/k will not be ready by the code freeze, so the alpha of this KEP will skip version 1.32. Therefore, I will close the following PR that was opened against the dev-1.32 branch of the k/website repository.
kubernetes/website#48382

[cupnes]

@rashansmith
As mentioned in the above comment, this KEP will skip version 1.32. Could I write the feature blog on version 1.33?

[dipesh-rawat]

Hello @cupnes 👋 v1.32 Enhancements team 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 v1.32 milestone.

If you still wish to progress this enhancement in v1.32, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/label tracked/no
/remove-label tracked/yes
/milestone clear

[cupnes]

@rashansmith
#4049 (comment)

Could I write the feature blog on version 1.33?

Regarding this matter, is it all right for me to expect to have the opportunity to write the feature blog for version 1.33? If so, I would like to start preparing early.

[dipesh-rawat]

Hello @cupnes 👋, 1.33 Enhancements Lead here.

If you'd like to work on this enhancement in v1.33, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.33 using /milestone v1.33.
Thanks!

/remove-label lead-opted-in

[cupnes]

@dipesh-rawat
Thank you. Yes, I'd like to work on this enhancement alpha version in v1.33.

/add-label lead-opted-in
/milestone v1.33

[k8s-ci-robot]

@cupnes: 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:

@dipesh-rawat
Thank you. Yes, I'd like to work on this enhancement alpha version in v1.33.

/add-label lead-opted-in
/milestone v1.33

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.

[cupnes]

@xing-yang @dipesh-rawat
Could you please add the following labels? I couldn't do that.

/add-label lead-opted-in
/milestone v1.33

[xing-yang]

@cupnes I added the labels.

[lzung]

Hello @cupnes 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage alpha for v1.33 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.33.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• Can you please update your KEP readme to use the latest template, and make sure to fill out all required sections?
• It is missing the Risks and Mitigations section after Notes/Constraints/Caveats

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[dipesh-rawat]

Hi @cupnes 👋, 1.33 Enhancements team here,

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

The current status of this enhancement is marked as At risk for enhancement freeze. There are a few requirements mentioned in the comment #4049 (comment) that still need to be completed.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!