User Story

As an OpenShift administrator, I would like vShere CSI Driver Operator to not become degraded due to vSphere Multi vCenter feature gate being enabled so that I can begin to install my cluster across multiple vcenters and create PVs.

Description

The purpose of this story is to perform the needed changes to get vShere CSI Driver Operator allowing the configuration of the new Feature Gate for vSphere Multi vCenter support.  By default, the operator will still only allow one vCenter definition and support that config; however, once the feature gate for vSphere Multi vCenter is enabled, we will allow more than one vCenter.  Initially, the plan is to only allow a max of 3 vCenter definitions which will be controlled via the CRD for the vSphere infrastructure definitions.

Required:

The vShere CSI Driver Operator after install must not fail due to the number of vCenters configured.  The operator will also need to allow the creation of PVs.  Any other failure reported based on issues performing operator tasks is valid and should be addressed via a new story.

ACCEPTANCE CRITERIA

• multi vcenter enabled: Operator is not degraded from having more than one vCenter defined in the infrastructure custom resource
• multi vcenter disabled: Operator will become degraded if vCenter count is greater than 1

ENGINEERING DETAILS

• Migrate operator to use new YAML cloud config
• Fix csi driver controller roles to include correct permissions
• Update openshift/api to be >= version with new VSphereMultiVCenters feature gate
• Enhance operator to be able to monitor feature gates
• Enhance operator to support multiple vCenters
  • apply tags
  • create storage policies
• Update all check logic
• Update pod creation to not use env var and put user/pass in config.  ENV vars do not allow for mulitple user/pass to allow communication w/ multiple vCenters