Merge pull request #29499 from gnufied/update-vmotion-docs

Author: Bob Furu

modules/installation-vsphere-infrastructure.adoc

@@ -26,11 +26,7 @@ You must install the {product-title} cluster on a VMware vSphere version 6 or 7
 
 |Storage with in-tree drivers
 |vSphere 6.5 and later
-|This plug-in creates vSphere storage by using the in-tree storage drivers for vSphere included in {product-title} and can be used when vSphere CSI drivers are not available.
-
-|Storage with vSphere CSI driver
-|vSphere 6.7U3 and later
-|This plug-in creates vSphere storage by using the standard Container Storage Interface. The vSphere CSI driver is provided and supported by VMware.
+|This plug-in creates vSphere storage by using the in-tree storage drivers for vSphere included in {product-title}.
 
 |===
 
@@ -41,8 +37,3 @@ you install {product-title}.
 ====
 You must ensure that the time on your ESXi hosts is synchronized before you install {product-title}. See link:https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-8756D419-A878-4AE0-9183-C6D5A91A8FB1.html[Edit Time Configuration for a Host] in the VMware documentation.
 ====
-
-[IMPORTANT]
-====
-A limitation of using VPC is that the Storage Distributed Resource Scheduler (SDRS) is not supported. See link:https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/faqs.html[vSphere Storage for Kubernetes FAQs] in the VMware documentation.
-====

modules/installation-vsphere-installer-infra-requirements.adoc

@@ -40,6 +40,19 @@ A user requires the following privileges to install an {product-title} cluster:
 
 For more information about creating an account with only the required privileges, see link:https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-5372F580-5C23-4E9C-8A4E-EF1B4DD9033E.html[vSphere Permissions and User Management Tasks] in the vSphere documentation.
 
+[discrete]
+[id="installation-vsphere-installer-infra-requirements-vmotion_{context}"]
+== Using {product-title} with vMotion
+
+[IMPORTANT]
+====
+{product-title} generally supports compute-only vMotion. Using Storage vMotion can cause issues and is not supported.
+====
+
+If you are using vSphere volumes in your pods, migrating a VM across datastores either manually or through Storage vMotion causes invalid references within {product-title} persistent volume (PV) objects. These references prevent affected pods from starting up and can result in data loss.
+
+Similarly, {product-title} does not support selective migration of VMDKs across datastores, using datastore clusters for VM provisioning or for dynamic or static provisioning of PVs, or using a datastore that is part of a datastore cluster for dynamic or static provisioning of PVs.
+
 [discrete]
 [id="installation-vsphere-installer-infra-requirements-resources_{context}"]
 == Cluster resources