1. Proposed title of this feature request

4.13 docs do not show how to setup the vSphere CSI driver on new installations

2. What is the nature and description of the request?

In previous releases of OCP (4.12 and below), the vSphere CSI driver was installed and readily available for customers to attach storage using the `thin` storage class.

4.12 and below:

oc get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
thin (default) kubernetes.io/vsphere-volume Delete Immediate false 3d20h
thin-csi csi.vsphere.vmware.com Delete WaitForFirstConsumer true 3d20h

With the in-tree drivers now removed with new installations of OCP 4.13+, the `thin` storage class is now unavailable:

4.13:

oc get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
thin-csi (default) csi.vsphere.vmware.com Delete WaitForFirstConsumer true 18h

3. Why does the customer need this? (List the business requirements here)

The documentation currently does not state this behavior of new installations removing the thin storage class which were originally part of the in-tree driver installation in previous OCP releases. Customers need detailed instructions on how to properly install the driver to allocate storage on new installations of OCP 4.13 on vSphere.

4. List any affected packages or components.