Epic Goal

Support upstream feature "VolumeAttributesClass" in OCP as GA, i.e. test it and have docs for it.

Also throw a warning if the attribute change introduces an unexpected change on the volume.

Example:

• VAC A has iops: 10 __ (implying throughput: 5 GBPS as the default)
• VAC B has iops: 20 and throughput: 10 GBPS

When the user moves a volume from VAC A to B and then back to A, the volume may end up with  throughput: 10 GBPS in some error cases and it’s wrong. The user does not know about it and they get charged for 10 GBPS. VAC A should have explicit throughput: 5 GBPS to reset any parameters that VAC B applied.

Why is this important?

• We get this upstream feature through Kubernetes rebase. We should ensure it works well in OCP and we have docs for it.

Upstream links

• Enhancement issue: https://github.com/kubernetes/enhancements/issues/3751
• KEP: https://github.com/kubernetes/enhancements/pull/3780

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>