enhancements

enhancements copied to clipboard

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.32
  • Beta release target (x.y):
  • Stable release target (x.y):
• [ ] Alpha
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/4042
  • [ ] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/128184
  • [ ] Docs (k/website) update PR(s): https://github.com/kubernetes/website/pull/48382

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

/sig storage

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

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

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

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

/remove-lifecycle stale

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

/remove-lifecycle stale

/milestone v1.32

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

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (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.32.
• [ ] 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 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

• Create the KEP readme using the latest template and merge it in the k/enhancements repo.
• Ensure that the KEP has undergone a production readiness review and has been merged into k/enhancements.

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

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

@dipesh-rawat I have completed the tasks outlined in this document and am currently waiting for the PRR review.

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

I understood. Thank you.

@dipesh-rawat Since it seems that the PRR for this enhancement will not be completed by the PRR Freeze deadline, I will stop aiming for the alpha stage of v1.32. Please remove this enhancement from the list of enhancements for v1.32.

Hi @cupnes , the 10/3 PRR deadline is for the PRR section to be filled out and ready to review. So you still have until 10/10, the KEP freeze deadline, for the PRR section to be approved.

@xing-yang Thank you for the information. I've changed it back to 1.32.

@dipesh-rawat As stated above, this KEP is targeted to 1.32.