Merge pull request #42648 from lpettyjo/OSDOCS-3192

OSDOCS-3192: vSphere install requirements (adding to storage content area)

Author: lpettyjo

modules/persistent-storage-csi-vsphere-install-issues.adoc

@@ -4,22 +4,22 @@
 //
 
 [id="persistent-storage-csi-vsphere-install-issues_{context}"]
-= Removing a non-Red Hat vSphere CSI Operator Driver
+= Removing a third-party vSphere CSI Operator Driver
 
 {product-title} 4.10 includes a built-in version of the vSphere CSI Operator Driver that is supported by Red Hat. If you have installed a vSphere Container Storage Interface (CSI) Driver provided by the community or another vendor, updates to the next major version of {product-title}, such as 4.11, might be disabled for your cluster.
 
-{product-title} 4.10 clusters are still fully supported, and updates to z-stream releases of 4.10, such as 4.10.z, are not blocked, but you must correct this state by removing the non-Red Hat vSphere CSI Driver before updates to next major version of {product-title} can occur. Removing the non-Red Hat vSphere CSI driver does not require deletion of associated persistent volume (PV) objects, and no data loss should occur.
+{product-title} 4.10 clusters are still fully supported, and updates to z-stream releases of 4.10, such as 4.10.z, are not blocked, but you must correct this state by removing the third-party vSphere CSI Driver before updates to next major version of {product-title} can occur. Removing the third-party vSphere CSI driver does not require deletion of associated persistent volume (PV) objects, and no data loss should occur.
 
 [NOTE]
 ====
 These instructions may not be complete, so consult the vendor or community provider uninstall guide to ensure removal of the driver and components.
 ====
 
-To uninstall the non-Red Hat vSphere CSI Driver:
+To uninstall the third-party vSphere CSI Driver:
 
-. Delete the non-Red Hat vSphere CSI Driver (VMware vSphere Container Storage Plug-in) Deployment and Daemonset objects.
-. Delete the configmap and secret objects that were installed previously with the non-Red Hat vSphere CSI Driver.
-. Delete the non-Red Hat vSphere CSI driver `CSIDriver` object:
+. Delete the third-party vSphere CSI Driver (VMware vSphere Container Storage Plug-in) Deployment and Daemonset objects.
+. Delete the configmap and secret objects that were installed previously with the third-party vSphere CSI Driver.
+. Delete the third-party vSphere CSI driver `CSIDriver` object:
 +
 [output, terminal]
 ----
@@ -31,4 +31,4 @@ To uninstall the non-Red Hat vSphere CSI Driver:
 csidriver.storage.k8s.io "csi.vsphere.vmware.com" deleted
 ----
 
-After you have removed the non-Red Hat vSphere CSI Driver from the {product-title} cluster, installation of Red Hat's vSphere CSI Operator Driver automatically resumes, and any conditions that could block upgrades to {product-title} 4.11, or later, are automatically removed. If you had existing vSphere CSI PV objects, their lifecycle is now managed by Red Hat's vSphere CSI Operator Driver.
+After you have removed the third-party vSphere CSI Driver from the {product-title} cluster, installation of Red Hat's vSphere CSI Operator Driver automatically resumes, and any conditions that could block upgrades to {product-title} 4.11, or later, are automatically removed. If you had existing vSphere CSI PV objects, their lifecycle is now managed by Red Hat's vSphere CSI Operator Driver.

storage/container_storage_interface/persistent-storage-csi-vsphere.adoc

@@ -36,6 +36,9 @@ include::modules/persistent-storage-csi-about.adoc[leveloffset=+1]
 
 include::modules/persistent-storage-csi-vsphere-stor-policy.adoc[leveloffset=+1]
 
+[id="vsphere-csi-driver-requirements_{context}"]
+include::snippets/vmware-csi-driver-reqs.adoc[leveloffset=+1]
+
 include::modules/persistent-storage-csi-vsphere-install-issues.adoc[leveloffset=+1]
 
 :FeatureName: vSphere