Mutable CSINode Allocatable Property

[torredil]

Enhancement Description

• One-line enhancement description (can be used as a release note): CSI drivers can now dynamically adjust the maximum number of attachable volumes at runtime.
• Kubernetes Enhancement Proposal: KEP-4876: Mutable CSINode Allocatable Property #4875
• Discussion Link: Kubernetes SIG Storage - Bi-Weekly Meeting 2024-08-08: https://youtu.be/-X1bK-g209s?si=Dknuj64D1tvm91s6&t=809
• Primary contact (assignee): @torredil
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y): 1.34
  • Stable release target (x.y): 1.36
• Alpha v1.33
  • KEP (k/enhancements) PR(s): KEP-4876: Mutable CSINode Allocatable Property #4875
  • Code (k/k) PR(s): Implement KEP 4876 Mutable CSINode kubernetes#130007
  • Docs (k/website) PR(s):
    • Add docs for KEP-4876: Mutable CSINode Allocatable Property website#49918
    • sig-storage: Blog for KEP 4876 Mutable CSI CSINode Allocatable website#50016
• Beta v1.34
  • KEP (k/enhancements) update PR(s): Update KEP-4876 Mutable CSINode Allocatable for Beta #5386
  • Code (k/k) update PR(s):
    • Populate VolumeError.ErrorCode field in VolumeAttachment object kubernetes-csi/external-attacher#662
    • Reject pod when attachment limit is exceeded kubernetes#132933
    • Implement CSI e2e test for MutableCSINodeAllocatableCount kubernetes#130942
    • Use Mock CSI Driver for MutableCSINodeAllocatableCount storage e2e test kubernetes#132373
    • Promote sig-storage feature MutableCSINodeAllocatableCount to Beta kubernetes#132429
  • Docs (k/website) update(s):
    • Update docs for MutableCSINodeAllocatableCount website#51397
    • sig-storage: Mutable CSI Node Allocatable Blog Graduates to Beta website#51536
• Stable
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
    • Add Kubelet stress test for pod cleanup when rejection due to VolumeAttachmentLimitExceeded kubernetes#133357
  • Docs (k/website) update(s):

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

[torredil]

/sig storage

[xing-yang]

/milestone v1.32

[dipesh-rawat]

Hello @torredil 👋, 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!

[torredil]

@dipesh-rawat Thank you for the heads up. The KEP readme was created using the latest template linked above. If there is anything missing, please let me know.

[dipesh-rawat]

Hi @torredil 👋, v1.32 Enhancements team here.

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

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

It looks like PR #4875 will address most of these issues. The PR #4875 needs to be merged before the enhancements freeze.

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

[tjons]

Hello 👋, v1.32 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in 1.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!