Epic Goal*

Run e2e tests with in-tree in-line and pre-provisioned volumes

Why is this important? (mandatory)

We still support in-tree volumes, even though they were migrated to CSI. We should have e2e tests for them.

We lost these tests upstream when we removed the cloud providers from kubernetes/kubernetes.

Upstream issue: https://github.com/kubernetes/kubernetes/issues/118360. There were some attempts to fix it, but nobody has completed it yet. 
Scenarios (mandatory) 

1. As Kubernetes developer, I want to make sure my PR does not break support of in-line or pre-provisioned in-tree volumes.
2. As OCP developer, I want to make sure my PR does not break support of in-line or pre-provisioned in-tree volumes.

Dependencies (internal and external) (mandatory)

The largest part of this epic needs to be done upstream.

Contributing Teams(and contacts) (mandatory) 

• Development - 
• QE - 

Acceptance Criteria (optional)

Both Kubernetes and OCP runs e2e tests for in-tree in-line and pre-provisioned volumes.

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”