Epic Goal*

Today, we run separate CI jobs each CSI driver. Each job installs a cluster, runs the tests for a single driver and destroys the cluster.

We want to run tests for multiple CSI drivers inside a single cluster - like install Azure cluster and run tests for both Azure Disk and Azure File there.

 
Why is this important? (mandatory)

It would save us some money and time in CI, installing a fresh cluster for each CSI driver looks like waste of time.

Scenarios (mandatory) 

1. Periodic jobs tests as many CSI drivers using a single cluster. Idea:
   1. AWS: tests AWS EBS and AWS EFS (and Samba and SecretStore, if possible) in a single cluster
   2. Azure: Azure Disk, Azure File
   3. Google: GCP Disk, GCP Filestore
2. Pre-submit jobs in CSI driver repos runs tests just for the CSI driver that is being updated, for example:
   1. PR in aws-ebs-csi-driver repo runs tests only for EBS and not for EFS or Samba or SecretStore
3. Pre-submit jobs in csi-operator repo can test multiple drivers in a single job, such as:
   1. AWS: tests AWS EBS and AWS EFS (and Samba and SecretStore, if possible) in a single cluster
   2. Azure: Azure Disk, Azure File

 
Dependencies (internal and external) (mandatory)

This is just reshuffling our CI jobs. We do not propose to remove or add any tests, just run them in different jobs.

Contributing Teams(and contacts) (mandatory) 

• Development - 
• QE - 

Acceptance Criteria (optional)

Provide some (testable) examples of how we will know if we have achieved the epic goal.  

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”