Epic Goal*

• Add Kubernetes e2e test that as a CSI driver to provision a small volume and checks that the CSI driver increased the volume size to the nearest size supported by the driver.
  • For example, provisioning of 100 MB volume by AWS EBS CSI driver with volume type "io2" should provision 4GiB volume, because that's the smallest size supported by "io2". The provisioning should not fail with an error.
• Fix all CSI drivers that we ship as part of OCP and fail the test. Currently we know only about AWS EBS.

We will get the test in OCP via some a future Kubernetes rebase.

Why is this important? (mandatory)

This check behavior expected by the CSI spec.

It will allow users not to worry about their PVC sizes, as they can be always sure something will be provisioned and they don't need custom code (custom YAML files) for different CSI drivers.

This will also allow CNV to remove their custom code for AWS EBS that knows that they need to ask for 4GiB, because the CSI driver does not bump smaller sizes.

 
Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. As CSI driver vendor, I can run upstream e2e tests to detect that my CSI driver implements the CSI spec correctly.
2. After Kubernetes rebase in OCP: as 3rd party CSI driver vendor, I can run OCP's CSI certification suite to detect that my CSI driver implements the CSI spec correctly
3. As CNV engineer, I don't need a custom code for provisioning of small volumes on AWS.

 
Dependencies (internal and external) (mandatory)

Contributing Teams(and contacts) (mandatory) 

• Development - 
• QE - (or CI) after Kubernetes rebase - all our CSI drivers will need to pass the test. We already have CI jobs for that.

Acceptance Criteria (optional)

Drawbacks or Risk (optional)

Done - Checklist (mandatory)