Add e2e tests for PowerVS CSI Driver about ibm-powervs-block-csi-driver

[Madhan-SWE]

/assign

[Madhan-SWE]

• Exploring Amazon EBS CSI Driver e2e test cases
• Setting up the e2e suite for Power VS CSI Driver (e2e suite with pre provisioned volumes)
• Debugging issues in the sample test case

[Madhan-SWE]

Updates:

• Working on the sample test case - volume attachment was failing as the cluster health was not ok
• Switched to upstream resource group and deployed a new Kubernetes cluster
• Installed CSI Driver on the new cluster in upstream-core-lon04 resource group and deployed sample application
• Sample application deployment fails as volume attachment fails with the error

Warning  ProvisioningFailed    2s (x3 over 5s)  powervs.csi.ibm.com_powervs-csi-controller-56d978f56f-v75k9_d1c4f97d-565c-46e2-be90-59869eaaf739  failed to provision volume with StorageClass "powervs-sc": rpc error: code = Internal desc = Could not create volume "pvc-926dfeca-800a-4d8a-b3ee-b28327ef7bbb": invalid PowerVS VolumeType "Tier3-Flash-1"

• Volume created from the script matches with the tier of the cloud instance, But it doesn't match with Flash type
• Debugging create volume with power vs rest APIs

[Madhan-SWE]

Updates:

• Debugged tier mismatch issues from web console and explored the graphql request
• Explored Rest API docs for creating data volume in power vs
• Manually tried creating volumes and attaching to instance using curl
• Exploring affinity properties of data volume creation
• Explored power go client to create volume with affinity and found that there is no support available.
• Created the following issue to get support for create volumes with affinity attributes : IBM-Cloud/power-go-client#91

[Madhan-SWE]

Updates:

Explored IBM Cloud docs for storage affinity.
Solution for volume attachment issues:

• updated each and every node of our kubernetes cluster’s storagePoolAffinity property to false
• no changes needed in the power go client
  Explored shareable option for volume creation

[Madhan-SWE]

Updates
Completed sample pre provisioning test case
Completed below dynamic provisioning test cases:

• should create a volume on demand with provided mountOptions
• should create multiple PV objects, bind to PVCs and attach all to a single pod
• should create multiple PV objects, bind to PVCs and attach all to different pods
• should create a raw block volume on demand
• should create a raw block volume and a filesystem volume on demand and bind to the same pod
• should create multiple PV objects, bind to PVCs and attach all to different pods on the same node
• should create a volume on demand and mount it as readOnly in a pod
• should create a volume on demand with different volume type and different fs types (iterative test)
• should delete PV with reclaimPolicy delete
• should retain PV with reclaimPolicy retain
• should create a deployment object, write and read to it, delete the pod and write and read to it again
• should create a volume on demand and resize it
• should allow for topology aware volume scheduling

Faced issues in volume resize test case, raised the following issue: #4