Epic Goal*

Get involved into development of an upstream feature VolumeAttributesClass.

• To get familiar with the feature upstream before it gets into OCP.
• To prepare / anticipate the feature for inclusion in OCP.
• To present OpenShift's point of view upstream, so it works in OCP smoothly.
• To ensure the feature has good enough quality - has sane error messages, has e2e tests that we can run easily in OCP, has good enough documentation upstream, etc.
• To help upstream. If not getting influence (approval rights), then at least be seen a a valuable part of the community, so our voice is heard when needed.
• Internal knowledge sharing

Upstream enhancement issue: https://github.com/kubernetes/enhancements/issues/3751 

Upstream enhancement: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/3751-volume-attributes-class/README.md 
(Beware, there may be open PRs against the enhancement!)

Why is this important? (mandatory)

The feature will land in OCP sooner or later. We need to ensure the feature is good enough for OCP and we know how to integrate it there.

Scenarios (mandatory) 

At least:

• Review upstream enhancement.
• Try to run the feature in a Kubernetes cluster, poke around and see how it behaves.
• Try to run the feature in OCP - is there anything that needs to change in the upstream feature? What needs to be done on OCP side to bring the feature?
• Ensure there are e2e tests, check how they run and consider what would need to be done to run them in OCP.
• Help upstream to bring the feature to Alpha/Beta/GA. 

Dependencies (internal and external) (mandatory)

None

Contributing Teams(and contacts) (mandatory) 

• Development - 
• QE - 

Acceptance Criteria (optional)

Drawbacks or Risk (optional)

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be "Release Pending"