• Future Sustainability
    • None
    • 0% To Do, 100% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • XS

      Feature Overview (aka. Goal Summary)  

      K8s 1.34 introduces VolumeAttributesClass as GA (code in external provisioner). We should make it available to customers as GA.

      VolumeAttributesClass allows PVC to be modified after their creation and while attached. There is as vast number of parameters that can be updated but the most popular is to change the QoS values. Parameters that can be changed depend on the driver.

      Goals (aka. expected user outcomes)

      Productise VolumeAttributesClass as GA in anticipation for GA.

      Requirements (aka. Acceptance Criteria):

      • Enabled by default - remove feature gate
      • put it under TechPreviewNoUpgrade
      • make sure VolumeAttributeClass object is available with GA API
      • Current CI continues to be green

       

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both both
      Classic (standalone cluster) yes
      Hosted control planes yes
      Multi node, Compact (three node), or Single node (SNO), or all all
      Connected / Restricted Network both
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) all
      Operator compatibility N/A core storage
      Backport needed (list applicable versions) None
      UI need (e.g. OpenShift Console, dynamic plugin, OCM) TBD
      Other (please specify) n/A

      Use Cases (Optional):

      As an OCP user, I want to change parameters of my existing PVC such as the QoS attributes.

      Questions to Answer (Optional):

      Get list of drivers that supports it (from the ones we ship)

      Out of Scope

      No UI for TP

      Background

      There's been some limitations and complains on the fact that PVC attributes are sealed after their creation avoiding customers to update them. This is particularly impacting for a specific QoS is set and the volume requirements are changing.

      Customer Considerations

      Customer should not use it in production atm. The driver used by customers must support this feature. 

      Documentation Considerations

      Document VolumeAttributesClass creation and how to update PVC. Mention any limitation. Mention it's tech preview no upgrade. Add drivers support if needed.

      Interoperability Considerations

      Check which drivers support it for which parameters.

              rh-gs-gcharot Gregory Charot
              rh-gs-gcharot Gregory Charot
              None
              None
              Jan Safranek Jan Safranek
              Jan Safranek Jan Safranek
              Wei Sun Wei Sun
              Lisa Pettyjohn Lisa Pettyjohn
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: