Merge pull request #48911 from lpettyjo/OSDOCS-3783

OSDOCS-3783: GCP auto migration TP->GA

Author: lpettyjo

modules/persistent-storage-csi-migration-automatic-ga.adoc

@@ -14,6 +14,8 @@
 
 * Amazon Web Services (AWS) Elastic Block Storage (EBS)
 
+* Google Compute Engine Persistent Disk (GCP PD)
+
 CSI migration for these volume types is considered generally available (GA), and requires no manual intervention.
 
 For new {product-title} 4.11, and later, installations, the default storage class is the CSI storage class. All volumes provisioned using this storage class are CSI persistent volumes (PVs).

modules/persistent-storage-csi-migration-enable.adoc

@@ -8,8 +8,6 @@
 
 If you want to test Container Storage Interface (CSI) migration in development or staging {product-title} clusters, you must manually enable in-tree to CSI migration for the following in-tree volume types:
 
-* Google Compute Engine Persistent Disk (GCE-PD)
-
 * VMware vSphere Disk
 
 * Azure File
@@ -47,16 +45,14 @@ spec:
   featureSet: TechPreviewNoUpgrade <1>
 ...
 ----
-<1> Enables automatic migration for GCP, Azure File, and VMware vSphere.
+<1> Enables automatic migration for Azure File and VMware vSphere.
 +
 You can specify CSI automatic migration for a selected CSI driver by setting `CustomNoUpgrade` `featureSet` and for `featuregates` to one of the following:
 +
 --
 
 * CSIMigrationAzureFile
 
-* CSIMigrationGCE
-
 * CSIMigrationvSphere
 --
 +

modules/persistent-storage-csi-migration-overview.adoc

@@ -19,12 +19,12 @@ a|
 * Azure Disk
 * OpenStack Cinder
 * Amazon Web Services (AWS) Elastic Block Storage (EBS)
+* Google Compute Engine Persistent Disk (GCP PD)
 |Generally available (GA)
 | Yes. For more information, see "_Automatic migration of in-tree volumes to CSI_".
 
 a|
 * Azure File
-* Google Compute Engine Persistent Disk (in-tree) and Google Cloud Platform Persistent Disk (CSI)
 * VMware vSphere
 |Techology Preview (TP)
 | No. To enable, see "_Manually enabling CSI automatic migration_".