Merge pull request #56751 from jeana-redhat/OSDOCS-5013-CPMS-GCP-support-matrix

[OSDOCS-5013]: GCP CPMS support implementation details

Author: jeana-redhat

machine_management/control_plane_machine_management/cpmso-getting-started.adoc

@@ -9,16 +9,10 @@ toc::[]
 The process for getting started with the Control Plane Machine Set Operator depends on the state of the `ControlPlaneMachineSet` custom resource (CR) in your cluster.
 
 Clusters with an active generated CR:: Clusters that have a generated CR with an active state use the Operator by default. No administrator action is required.
-//+
-//AWS clusters that are created with {product-title} version 4.12 or later use the Control Plane Machine Set Operator by default.
 
 Clusters with an inactive generated CR:: For clusters that include an inactive generated CR, you must review the CR configuration and xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.adoc#cpmso-activating_cpmso-getting-started[activate the CR].
-//+
-//AWS clusters that are upgraded to {product-title} version 4.12 or later from an earlier version include an inactive generated CR.
 
 Clusters without a generated CR:: For clusters that do not include a generated CR, you must xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.adoc#cpmso-creating-cr_cpmso-getting-started[create and activate a CR] with the appropriate configuration for your cluster.
-//+
-//For Azure and VMware vSphere clusters
 
 If you are uncertain about the state of the `ControlPlaneMachineSet` CR in your cluster, you can xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.adoc#cpmso-checking-status_cpmso-getting-started[verify the CR status].
 
@@ -39,6 +33,11 @@ The status of the Operator after installation depends on your cloud provider and
 |X
 |
 
+|Google Cloud Platform (GCP)
+|X ^[2]^
+|X
+|
+
 |Microsoft Azure
 |X ^[2]^
 |X
@@ -52,7 +51,7 @@ The status of the Operator after installation depends on your cloud provider and
 [.small]
 --
 1. AWS clusters that are upgraded from version 4.11 or earlier require xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.adoc#cpmso-activating_cpmso-getting-started[CR activation].
-2. Azure clusters that are upgraded from version 4.12 or earlier require xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.adoc#cpmso-activating_cpmso-getting-started[CR activation].
+2. GCP and Azure clusters that are upgraded from version 4.12 or earlier require xref:../../machine_management/control_plane_machine_management/cpmso-getting-started.adoc#cpmso-activating_cpmso-getting-started[CR activation].
 --
 
 //Checking the Control Plane Machine Set Operator status
@@ -72,5 +71,6 @@ include::modules/cpmso-creating-cr.adoc[leveloffset=+1]
 .Additional resources
 * xref:../../machine_management/control_plane_machine_management/cpmso-configuration.adoc#cpmso-configuration[Control Plane Machine Set Operator configuration]
 * xref:../../machine_management/control_plane_machine_management/cpmso-configuration.adoc#cpmso-sample-yaml-aws_cpmso-configuration[Sample YAML for configuring Amazon Web Services clusters]
+* xref:../../machine_management/control_plane_machine_management/cpmso-configuration.adoc#cpmso-sample-yaml-gcp_cpmso-configuration[Sample YAML for configuring Google Cloud Platform clusters]
 * xref:../../machine_management/control_plane_machine_management/cpmso-configuration.adoc#cpmso-sample-yaml-azure_cpmso-configuration[Sample YAML for configuring Microsoft Azure clusters]
-//todo:* [Sample YAML for configuring VMware vSphere clusters]
+* xref:../../machine_management/control_plane_machine_management/cpmso-configuration.adoc#cpmso-sample-yaml-vsphere_cpmso-configuration[Sample YAML for configuring VMware vSphere clusters]