Kubernetes VolumeAttributesClass ModifyVolume

[sunnylovestiramisu]

Enhancement Description

• One-line enhancement description (can be used as a release note): An extension to the Kubernetes Persistent Volume API to allow users to dynamically control volume options iops + throughput.

• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/3751-volume-attributes-class/README.md

• Discussion Link:

• CSI Spec for ModifyVolume
• keps/sig-storage/3751-volume-attributes-class
• KEP-3751: Fix the definition of the VolumeAttributesClass #4116

• Primary contact (assignee): @mattcary @sunnylovestiramisu
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.29
  • Beta release target (x.y): 1.31
  • Stable release target (x.y): 1.3x
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3751: Kubernetes VolumeAttributesClass ModifyVolume #3780
    • Update Graduation Criteria for kep-3751 #4245
    • Update ControllerModifyVolume Status API #4298
  • Code (k/k) update PR(s):
    • v1.29: [KEP-3751] introduce the VolumeAttributesClass API kubernetes#121104
    • Pass VolumeAttributesClass Parameters as MutableParameters to CreateVolume kubernetes-csi/external-provisioner#1068
  • Docs (k/website) update PR(s):
    • v1.29: Add docs about VolumeAttributesClass API (KEP-3751) website#43463
    • 1.29 - Add a blog post about VolumeAttributesClass website#43777

• Beta
  • KEP (k/enhancements) update PR(s): KEP-3751: Update for milestone 1.31 #4698
  • Code (k/k) update PR(s):
    • vac add e2e test kubernetes#121849
    • [kep-3751] pvc bind pv with vac kubernetes#121902
    • Add labels to PVCollector bound/unbound PVC metrics for VolumeAttributesClass Feature#126166
    • [KEP-3751] Promote VolumeAttributesClass to beta #126145
    • Not required for 1.31 code freeze: A new controller adds/removes finalizer to VAC for protection kubernetes#123549
  • Docs (k/website) update(s): KEP-3751 VolumeAttributeClass Beta Promotion website#46785
  • Blog: Add post-release blog article for VAC beta website#46900

• Stable 1.34
  • KEP (k/enhancements) update PR(s):
    • KEP-3751: Update release signoff Checklist before GA #5024
  • Code (k/k) update PR(s):
    • Update VolumeAttributesClass API Description kubernetes#133040
    • [Kep-3751] Promote VolumeAttributesClass to GA kubernetes#131549
  • 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.

[sunnylovestiramisu]

/sig storage

[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

[sunnylovestiramisu]

/remove-lifecycle stale

[salehsedghpour]

Hello @sunnylovestiramisu 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023.

This enhancement is targeting for stage alpha for 1.28 (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: 1.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

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

• Update status to implementable in kep.yaml
• Add the test plan in the readme file
• Address questions inside the Production Readiness Review Questionnaire

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