Description

Enhance volume creation to use parameters based on the topology requirements for array. The CreateVolume request will check for the zone specific array ID and other parameters which have defaults in the secret if not specified in the storage class.

GitHub Issues

List the GitHub issues impacted by this PR:

Checklist:

• Have you run format,vet & lint checks against your submission?
• Have you made sure that the code compiles?
• Did you run the unit & integration tests successfully?
• Have you maintained at least 90% code coverage?
• Have you commented your code, particularly in hard-to-understand areas
• Have you done corresponding changes to the documentation
• Did you run tests in a real Kubernetes cluster?
• Backward compatibility is not broken

How Has This Been Tested?

Test cases:

1. Normal case of no labels on any nodes and secret has no zones. Validate that existing behavior is maintained.
2. Secret and nodes have zoning labels and validate that volumes are only provisioned in the zone that the node and array are in.
3. Upgrade from CSM 1.13 to CSM 1.14. The new style secret must not be in the driver namespace. Provision multiple pods/volumes on different nodes and on different arrays. Also include snapshot and clone test cases. Replication should also be tested.
4. New style secrets with no labels nor parameters. All array information (SYMID, ...) is in the storage class. Provisioning of all volume types should work as expected.
5. New style secrets with labels (no parameters) using one or more arrays. Storage class has complete storage array info. No nodes have matching labels. Attempt to provision volumes.
6. New style secrets with labels (no parameters) using one or more arrays. One node has matching labels but the other does not have any matching labels. Storage class has array info. Attempt to provision volumes with a pod.
7. New style secrets with labels (no parameters) using one array. Storage class has array info. Multiple nodes have matching labels. Attempt to provision multiple pods with multiple volumes. Validate that pods are distributed across nodes.
8. New style secrets with labels (no parameters) using one array. Storage class does not have array info. Multiple nodes have matching labels. Attempt to provision multiple pods with multiple volumes. Validate that pods are distributed across nodes.
9. New style secrets with labels (no parameters) multiple arrays in different zones. Storage classes do not have array info. Nodes have zoning for their respective array. Attempt to provision multiple pods with multiple volumes. Validate that pods are distributed across nodes according to what zone they are in.