Epic Goal*

This is implementation of CERTOPS-1040.

1. Enhance the CSI certification suite with a test that creates ~ 255 PVs and runs 255 pods with them on a single node in sequence. With some parallelism, like max 16 Pods running in parallel at max. ("255" and "16" should be somehow configurable).
2. When doing that, figure out how to add OCP specific tests into CSI certification suite, perhaps with custom configuration in test manifest. So CNV can add their tests to the CSI certification easily.

https://docs.google.com/document/d/1zdqCtfHqC3L_zv4VWJ8a8DyGvh5TsJSHqnR50oc1TeI/edit

 
Why is this important? (mandatory)

We have evidence that Dell CSI driver + RHCOS break after they provision more than 255 volumes, because RHCOS can't handle LUN IDs higher than 255 by default.

While RHCOS and Dell CSI driver might have been both fixed, we should have a generic test that checks a node can survive larger number of Pods (and volumes) used on it sequentially.

Scenarios (mandatory) 

• As CSI driver vendor, I want to make sure that my CSI driver does not break on RHCOS.
• As OCP vendor, I want to make sure certified CSI driver do not break with larger amount of Pods running with PVs.
• (side quest) As OCP engineer, I want to have an established way to add new tests to the CSI certification suite, esp. with new parameters for the test like total nr. of Pods to create and how many of them create in parallel.

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”