Adding private and existing vpc steps to initializing installation

Author: bscott-rh

modules/installation-initializing-manual.adoc

@@ -129,6 +129,19 @@ You must create a directory. Some installation assets, such as bootstrap X.509 c
 
 ifdef::gcp-private[]
 . Edit the `install-config.yaml` file to set the `publish: Internal` parameter.
+. Edit the `install-config.yaml` file to set the parameters necessary for installation into an existing VPC.
+.. Define the network and subnets for the VPC to install the cluster in under the parent `platform.gcp` field:
++
+[source,yaml]
+----
+platform:
+  gcp:
+    network: <existing_vpc>
+    controlPlaneSubnet: <control_plane_subnet>
+    computeSubnet: <compute_subnet>
+----
++
+For `platform.gcp.network`, specify the name for the existing Google VPC. For `platform.gcp.controlPlaneSubnet` and `platform.gcp.computeSubnet`, specify the existing subnets to deploy the control plane machines and compute machines, respectively.
 endif::gcp-private[]
 ifdef::gcp-shared[]
 . Edit the `install-config.yaml` file to set the parameters necessary for installation into a shared VPC.

modules/installation-initializing.adoc

@@ -69,6 +69,7 @@ ifeval::["{context}" == "installing-gcp-customizations"]
 endif::[]
 ifeval::["{context}" == "installing-gcp-vpc"]
 :gcp:
+:gcp-vpc:
 endif::[]
 ifeval::["{context}" == "installing-gcp-shared-vpc"]
 :gcp:
@@ -89,6 +90,7 @@ ifeval::["{context}" == "installing-restricted-networks-gcp"]
 endif::[]
 ifeval::["{context}" == "installing-restricted-networks-gcp-installer-provisioned"]
 :gcp:
+:gcp-restricted:
 :restricted:
 endif::[]
 ifeval::["{context}" == "installing-ibm-cloud-customizations"]
@@ -459,6 +461,20 @@ endif::aws-outposts[]
 ifndef::restricted,nutanix,aws-outposts[]
 . Modify the `install-config.yaml` file. You can find more information about the available parameters in the "Installation configuration parameters" section.
 endif::restricted,nutanix,aws-outposts[]
+ifdef::gcp-vpc[]
+.. Define the network and subnets for the VPC to install the cluster in under the parent `platform.gcp` field:
++
+[source,yaml]
+----
+platform:
+  gcp:
+    network: <existing_vpc>
+    controlPlaneSubnet: <control_plane_subnet>
+    computeSubnet: <compute_subnet>
+----
++
+For `platform.gcp.network`, specify the name for the existing Google VPC. For `platform.gcp.controlPlaneSubnet` and `platform.gcp.computeSubnet`, specify the existing subnets to deploy the control plane machines and compute machines, respectively.
+endif::gcp-vpc[]
 ifdef::three-node-cluster[]
 +
 [NOTE]
@@ -581,7 +597,7 @@ where:
 `<control_plane_subnet>`:: Replace `<control_plane_subnet>` with the existing subnet name to deploy the control plane machines.
 `<compute_subnet>:: Replace `<compute_subnet>` with the existing subnet name to deploy compute machines.
 endif::azure+restricted[]
-ifdef::gcp+restricted[]
+ifdef::gcp-restricted[]
 +
 .. Define the network and subnets for the VPC to install the cluster in under the parent `platform.gcp` field:
 +
@@ -595,7 +611,7 @@ platform:
 ----
 +
 For `platform.gcp.network`, specify the name for the existing Google VPC. For `platform.gcp.controlPlaneSubnet` and `platform.gcp.computeSubnet`, specify the existing subnets to deploy the control plane machines and compute machines, respectively.
-endif::gcp+restricted[]
+endif::gcp-restricted[]
 ifdef::ibm-power-vs+restricted[]
 +
 .. Define the network for the VPC to install the cluster in under the parent `platform.powervs` field:
@@ -766,6 +782,7 @@ ifeval::["{context}" == "installing-gcp-network-customizations"]
 endif::[]
 ifeval::["{context}" == "installing-gcp-vpc"]
 :!gcp:
+:!gcp-vpc:
 endif::[]
 ifeval::["{context}" == "installing-gcp-shared-vpc"]
 :!gcp:
@@ -783,6 +800,7 @@ ifeval::["{context}" == "installing-restricted-networks-gcp"]
 endif::[]
 ifeval::["{context}" == "installing-restricted-networks-gcp-installer-provisioned"]
 :!gcp:
+:!gcp-restricted:
 :!restricted:
 endif::[]
 ifeval::["{context}" == "installing-ibm-cloud-customizations"]

modules/private-clusters-about-gcp.adoc

@@ -7,7 +7,7 @@
 = Private clusters in {gcp-short}
 
 [role="_abstract"]
-To create a private cluster on {gcp-first}, you must provide an existing private VPC and subnets to host the cluster, and you must specify `publish: Internal` in your `install-config.yaml` file. The installation program must also be able to resolve the DNS records that the cluster requires. The installation program configures the Ingress Operator and API server for only internal traffic.
+To create a private cluster on {gcp-first}, you must provide an existing VPC network and subnets to host the cluster, and you must specify `publish: Internal` in your `install-config.yaml` file. The installation program must also be able to resolve the DNS records that the cluster requires. The installation program configures the Ingress Operator and API server for only internal traffic.
 
 The cluster still requires access to internet to access the {gcp-short} APIs.