USER STORY

As an OpenShift administrator, I would like to create PVs in a cluster that is installed across multiple vCenters so that I can have persistent storage my my custom workloads in addition to the core ones such as image registry.

DESCRIPTION:

The purpose of this story is to update the openshift fork of the vsphere-csi-driver to contain all functions of version 3.2 of the upstream project. We need to upgrade to version 3.2 in order to get volume topology feature for file volumes.  Currently if we try to create a PVC for thin storage in vsphere after adding the multi vCenter support, PVs will not get created due to the error:

E0423 18:09:15.871235       1 controller.go:957] error syncing claim "5dbd8760-8fc2-42c3-abed-013706d529f8": failed to provision volume with StorageClass "thin-csi": rpc error: code = InvalidArgument desc = volume topology feature for file volumes is not supported. 

This feature has been added to version 3.2 and can be read about here: https://github.com/kubernetes-sigs/vsphere-csi-driver/releases/tag/v3.2.0

ACCEPTANCE CRITERIA

• Operator installs controller pods without any issues (need to be aware of any/all rbac, role, etc updates)
• PVCs will result in creation of PVs by the controller (csi-provisioner)

ENGINEERING DETAILS

Need to discuss with CSO team on how this process is to occur.  I have generated a PoC where I merged the 3.2 changes into master and tested.