diff --git a/Gemfile b/Gemfile index d35b61512..0b7902972 100644 --- a/Gemfile +++ b/Gemfile @@ -1,3 +1,3 @@ source 'https://rubygems.org' -gem "github-pages", group: :jekyll_plugins +gem "github-pages", group: :jekyll_plugins \ No newline at end of file diff --git a/README.md b/README.md index e248f3382..9bdc57163 100644 --- a/README.md +++ b/README.md @@ -11,4 +11,3 @@ If this is your first interatction with Red Hat's Managed Openshift service offe For contributing to this repository, please follow the guidelines specified in the [contributing.md](./CONTRIBUTING.md) - diff --git a/content/_index.md b/content/_index.md index 6d7cfdb16..1de71fcd9 100644 --- a/content/_index.md +++ b/content/_index.md @@ -63,8 +63,10 @@ archetype: home ### GCP -* [Deploy OSD in GCP using Pre-Existent VPC and Subnets](/docs/gcp/osd_preexisting_vpc.md) -* [Using Filestore with OpenShift Dedicated in GCP](/docs/gcp/filestore.md) +* Deploy OSD in GCP using Pre-Existent VPC and Subnets + * [via CLI](/docs/gcp/osd_preexisting_vpc/osd_preexisting_vpc_cli.md) + * [via GUI](/docs/gcp/osd_preexisting_vpc/osd_preexisting_vpc_ui.md) +* [Using Filestore with OpenShift Dedicated in GCP](/docs/gcp/filestore) ## Advanced Cluster Manager (ACM) diff --git a/content/docs/gcp/_index.md b/content/docs/gcp/_index.md index 66920a8da..c2757c183 100644 --- a/content/docs/gcp/_index.md +++ b/content/docs/gcp/_index.md @@ -3,8 +3,7 @@ title: "OSD on Google Cloud" date: 2022-09-14 description: MOBB Docs and Guides for GCP archetype: chapter -tags: ["GCP", "OSD"] +weight: 2 --- -* [Filestore Storage for OSD on GCP](./filestore.md) -* [Creating OSD on GCP w/ Existing VPC](./osd_preexisting_vpc.md) \ No newline at end of file +###### OpenShift Dedicated is professionally managed by Red Hat and hosted on Amazon Web Services (AWS) or Google Cloud Platform (GCP). Each OpenShift Dedicated cluster comes with a fully managed control plane (Control and Infrastructure nodes), application nodes, installation and management by Red Hat Site Reliability Engineers (SRE), premium Red Hat Support, and cluster services such as logging, metrics, monitoring, notifications portal, and a cluster portal. \ No newline at end of file diff --git a/content/docs/gcp/filestore.md b/content/docs/gcp/filestore/_index.md similarity index 100% rename from content/docs/gcp/filestore.md rename to content/docs/gcp/filestore/_index.md diff --git a/content/docs/gcp/images/osd-gcp2.png b/content/docs/gcp/images/osd-gcp2.png deleted file mode 100644 index 9a3e50a73..000000000 Binary files a/content/docs/gcp/images/osd-gcp2.png and /dev/null differ diff --git a/content/docs/gcp/images/osd-gcp3.png b/content/docs/gcp/images/osd-gcp3.png deleted file mode 100644 index 6e3dc8c1c..000000000 Binary files a/content/docs/gcp/images/osd-gcp3.png and /dev/null differ diff --git a/content/docs/gcp/images/osd-gcp4.png b/content/docs/gcp/images/osd-gcp4.png deleted file mode 100644 index ea70ac11f..000000000 Binary files a/content/docs/gcp/images/osd-gcp4.png and /dev/null differ diff --git a/content/docs/gcp/images/osd-gcp5.png b/content/docs/gcp/images/osd-gcp5.png deleted file mode 100644 index 007605e5c..000000000 Binary files a/content/docs/gcp/images/osd-gcp5.png and /dev/null differ diff --git a/content/docs/gcp/images/osd-gcp9.png b/content/docs/gcp/images/osd-gcp9.png deleted file mode 100644 index 32039c2df..000000000 Binary files a/content/docs/gcp/images/osd-gcp9.png and /dev/null differ diff --git a/content/docs/gcp/osd_preexistent_vpc/_index.md b/content/docs/gcp/osd_preexistent_vpc/_index.md new file mode 100644 index 000000000..754829a4d --- /dev/null +++ b/content/docs/gcp/osd_preexistent_vpc/_index.md @@ -0,0 +1,4 @@ +--- +date: '2022-09-14T22:07:08.584151' +title: Creating a OSD in GCP with Existing VPCs +--- diff --git a/content/docs/gcp/images/osd-gcp1.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp1.png similarity index 100% rename from content/docs/gcp/images/osd-gcp1.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp1.png diff --git a/content/docs/gcp/images/osd-gcp10.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp10.png similarity index 100% rename from content/docs/gcp/images/osd-gcp10.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp10.png diff --git a/content/docs/gcp/images/osd-gcp11.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp11.png similarity index 100% rename from content/docs/gcp/images/osd-gcp11.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp11.png diff --git a/content/docs/gcp/images/osd-gcp12.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp12.png similarity index 100% rename from content/docs/gcp/images/osd-gcp12.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp12.png diff --git a/content/docs/gcp/images/osd-gcp13.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp13.png similarity index 100% rename from content/docs/gcp/images/osd-gcp13.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp13.png diff --git a/content/docs/gcp/images/osd-gcp14.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp14.png similarity index 100% rename from content/docs/gcp/images/osd-gcp14.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp14.png diff --git a/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp2.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp2.png new file mode 100644 index 000000000..468869a89 Binary files /dev/null and b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp2.png differ diff --git a/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp3.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp3.png new file mode 100644 index 000000000..da1a601b0 Binary files /dev/null and b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp3.png differ diff --git a/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp4.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp4.png new file mode 100644 index 000000000..0ccfef5fc Binary files /dev/null and b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp4.png differ diff --git a/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp5.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp5.png new file mode 100644 index 000000000..f39437004 Binary files /dev/null and b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp5.png differ diff --git a/content/docs/gcp/images/osd-gcp6.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp6.png similarity index 100% rename from content/docs/gcp/images/osd-gcp6.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp6.png diff --git a/content/docs/gcp/images/osd-gcp7.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp7.png similarity index 100% rename from content/docs/gcp/images/osd-gcp7.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp7.png diff --git a/content/docs/gcp/images/osd-gcp8.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp8.png similarity index 100% rename from content/docs/gcp/images/osd-gcp8.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-gcp8.png diff --git a/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp9.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp9.png new file mode 100644 index 000000000..4b6f7b317 Binary files /dev/null and b/content/docs/gcp/osd_preexistent_vpc/images/osd-gcp9.png differ diff --git a/content/docs/gcp/images/osd-prereqs.png b/content/docs/gcp/osd_preexistent_vpc/images/osd-prereqs.png similarity index 100% rename from content/docs/gcp/images/osd-prereqs.png rename to content/docs/gcp/osd_preexistent_vpc/images/osd-prereqs.png diff --git a/content/docs/gcp/osd_preexistent_vpc/osd_preexisting_vpc_cli.md b/content/docs/gcp/osd_preexistent_vpc/osd_preexisting_vpc_cli.md new file mode 100644 index 000000000..7f134d66c --- /dev/null +++ b/content/docs/gcp/osd_preexistent_vpc/osd_preexisting_vpc_cli.md @@ -0,0 +1,234 @@ +--- +date: '2022-09-14T22:07:08.594151' +title: Creating a OSD in GCP with Existing VPCs - CLI +aliases: ['/docs/gcp/osd_preexisting_vpc/osd_preexisting_vpc_cli.md'] +tags: ["GCP", "OSD"] +--- + +**Roberto Carratalá, Andrea Bozzoni** + +*Last updated 11/14/2022* + +This is a guide to install OSD in GCP within Existing Virtual Private Clouds (VPCs) using CLI tools (gcloud CLI) or Terraform. + +The guide will show all the steps to create all the networking prerequisites in GCP and then installing the OSD Cluster in GCP. + +> **Tip** The official documentation for installing a OSD cluster in GCP can be found [here](https://docs.openshift.com/dedicated/osd_cluster_create/creating-a-gcp-cluster.html). + +## Prerequisites + +* [gcloud CLI](https://cloud.google.com/sdk/gcloud) +* [jq](https://stedolan.github.io/jq/download/) + +NOTE: Also the GCloud Shell can be used, and have the gcloud cli among other tools preinstalled. + +## Generate GCP VPC and Subnets + +For deploy an OSD cluster in GCP using existing Virtual Private Cloud (VPC) you need to implement some prerequisites that you must create before starting the OpenShift Dedicated installation though the OCM. + +This is a diagram showing the GCP infra prerequisites that are needed for the OSD installation: + +![GCP Prereqs](../images/osd-prereqs.png) + +You can use the gcloud CLI, to deploy the GCP VPC and subnets among other prerequisites for install the OSD in GCP. + +As mentioned before, for deploy OSD in GCP using existing GCP VPC, you need to provide and create beforehand a GCP VPC and two subnets (one for the masters and another for the workers nodes). + +1. Login and configure the proper GCP project where the OSD will be deployed: + + ```sh + export PROJECT_NAME= + gcloud auth list + gcloud config set project $PROJECT_NAME + gcloud config list project + ``` + +2. Export the names of the vpc and subnets: + + ```sh + export REGION= + export OSD_VPC= + export MASTER_SUBNET= + export WORKER_SUBNET= + ``` + +3. Create a custom mode VPC network: + + ```sh + gcloud compute networks create $OSD_VPC --subnet-mode=custom + gcloud compute networks describe $OSD_VPC + ``` + +NOTE: we need to create the mode custom for the VPC network, because the auto mode generates automatically the subnets with IPv4 ranges with [predetermined set of ranges](https://cloud.google.com/vpc/docs/subnets#ip-ranges). + +4. This example is using the standard configuration for these two subnets: + + ```md + master-subnet - CIDR 10.0.0.0/17 - Gateway 10.0.0.1 + worker-subnet - CIDR 10.0.128.0/17 - Gateway 10.0.128.1 + ``` + +5. Create the GCP Subnets for the masters and workers within the previous GCP VPC network: + + ```sh + gcloud compute networks subnets create $MASTER_SUBNET \ + --network=$OSD_VPC --range=10.0.0.0/17 --region=$REGION + + gcloud compute networks subnets create $WORKER_SUBNET \ + --network=$OSD_VPC --range=10.0.128.0/17 --region=$REGION + ``` + + ![GCP VPC and Subnets](../images/osd-gcp1.png) + +6. Once the VPC and the two subnets are provided it is needed to create one [GCP Cloud Router](https://cloud.google.com/network-connectivity/docs/router/how-to/create-router-vpc-on-premises-network): + + ```sh + export OSD_ROUTER= + + gcloud compute routers create $OSD_ROUTER \ + --project=$PROJECT_NAME --network=$OSD_VPC --region=$REGION + ``` + + ![GCP Routers](../images/osd-gcp2.png) + +7. Then, we will deploy two [GCP Cloud NATs](https://cloud.google.com/nat/docs/set-up-manage-network-address-translation#gcloud) and attach them within the GCP Router: + + * Generate the GCP Cloud Nat for the Master Subnets: + + ```sh + export NAT_MASTER= + + gcloud compute routers nats create $NAT_MASTER \ + --region=$REGION \ + --router=$OSD_ROUTER \ + --auto-allocate-nat-external-ips \ + --nat-custom-subnet-ip-ranges=$MASTER_SUBNET + ``` + + ![GCP Nat Master](../images/osd-gcp3.png) + + * Generate the GCP Cloud NAT for the Worker Subnets: + + ```sh + export NAT_WORKER= + + gcloud compute routers nats create $NAT_WORKER \ + --region=$REGION \ + --router=$OSD_ROUTER \ + --auto-allocate-nat-external-ips \ + --nat-custom-subnet-ip-ranges=$WORKER_SUBNET + ``` + + ![GCP Nat Worker](../images/osd-gcp4.png) + +8. As you can check the Cloud NATs GW are attached now to the Cloud Router: + + ![GCP Nat Master](../images/osd-gcp5.png) + +## Install the OSD cluster using pre-existent VPCs using OCM-CLI + +[OCM CLI](https://github.com/openshift-online/ocm-cli) is a command line tool that simplifies the use of the OCM API available at . + +1. Define the variables needed for the OSD in GCP cluster creation: + +```bash +export CLUSTER_NAME= +export REGION= +export OSD_VPC= +export MASTER_SUBNET= +export WORKER_SUBNET= +``` + +2. You need to generate a [GCP Service Account and generate a new key](https://cloud.google.com/sdk/docs/authorizing#authorize_with_a_service_account). Then download the json file and export the path where is located: + +```bash +export GCP_SA_FILE= +``` + +> If the Service Account is generated beforehand (look for osd-ccs-admin service account), then you only need to generate a new key and download the json gcp Service Account file file. + +3. Create the cluster using the OCM-CLI: + +```bash +ocm create cluster $CLUSTER_NAME --provider gcp \ + --vpc-name $OSD_VPC --region $REGION \ + --control-plane-subnet $MASTER_SUBNET \ + --compute-subnet $WORKER_SUBNET \ + --service-account-file $GCP_SA_FILE --ccs +``` + +4. Check the cluster status using OCM-CLI: + +```bash +GCP_OSD_ID=$(ocm list clusters | grep $CLUSTER_NAME | awk '{ print $1 }') +ocm cluster status $GCP_OSD_ID +``` + +5. Enjoy your brand new OSD in GCP cluster! + +## Automated Deploy OSD VPC and Subnets using Terraform + +You can use also [automation code in Terraform](https://github.com/rh-mobb/tf-osd-gcp) to deploy all the GCP infrastructure required to deploy the OSD in preexistent VPCs and to deploy the OSD in GCP within the Preexistent VPCs. + +* Clone the tf-osd-gcp repository: + +```bash +git clone https://github.com/rh-mobb/tf-osd-gcp.git +cd tf-osd-gcp +``` + +* Copy and modify the tfvars file in order to custom to your scenario: + +```bash +cp -pr terraform.tfvars.example terraform.tfvars +``` + +* Deploy the network infrastructure in GCP needed for deploy the OSD cluster: + +```bash +make all +``` + +## Cleanup + +For cleaning up the cluster you need to delete first the OSD cluster and then all the Network Prereqs that you've deployed. + +### Using Gcloud CLI + +1. Delete the OSD cluster using option 1 or option 2: + + * Option 1: Deleting the OSD cluster can be done using the OCM console described in the [official OSD docs](https://docs.openshift.com/dedicated/osd_install_access_delete_cluster/creating-a-gcp-cluster.html). + + * Option 2: Delete OSD from CLI: + + ```bash + ocm delete cluster $GCP_OSD_ID + ``` + +2. Deleting the GCP infrastructure resources (VPC, Subnets, Cloud NAT, Cloud Router). +Depending of which option you selected you must perform: + +3. Delete GCP resources using GCloud CLI: + + ```sh + gcloud compute routers nats delete $NAT_WORKER \ + --region=$REGION --router=$OSD_ROUTER --quiet + + gcloud compute routers nats delete $NAT_MASTER \ + --region=$REGION --router=$OSD_ROUTER --quiet + + gcloud compute routers delete $OSD_ROUTER --region=$REGION --quiet + + gcloud compute networks subnets delete $MASTER_SUBNET --region=$REGION --quiet + gcloud compute networks subnets delete $WORKER_SUBNET --region=$REGION --quiet + + gcloud compute networks delete $OSD_VPC --quiet + ``` + +### Using Terraform + +1. Delete GCP resources using Terraform: + + ```sh + make destroy + ``` diff --git a/content/docs/gcp/osd_preexisting_vpc.md b/content/docs/gcp/osd_preexistent_vpc/osd_preexisting_vpc_ui.md similarity index 70% rename from content/docs/gcp/osd_preexisting_vpc.md rename to content/docs/gcp/osd_preexistent_vpc/osd_preexisting_vpc_ui.md index ee03fc708..b92b9cb0b 100644 --- a/content/docs/gcp/osd_preexisting_vpc.md +++ b/content/docs/gcp/osd_preexistent_vpc/osd_preexisting_vpc_ui.md @@ -1,17 +1,19 @@ --- date: '2022-09-14T22:07:08.594151' -title: Creating a OSD in GCP with Existing VPCs -aliases: ['/docs/gcp/osd_preexisting_vpc.md'] +title: Creating a OSD in GCP with Existing VPCs - GUI +aliases: ['/docs/gcp/osd_preexisting_vpc/osd_preexisting_vpc_ui.md'] tags: ["GCP", "OSD"] --- **Roberto Carratalá, Andrea Bozzoni** -*Last updated 07/06/2022* +*Last updated 11/14/2022* -> **Tip** The official documentation for installing a OSD cluster in GCP can be found [here](https://docs.openshift.com/dedicated/osd_cluster_create/creating-a-gcp-cluster.html). +This is a guide to install OSD in GCP within Existing Virtual Private Clouds (VPCs) using GCP and [OCM UI](https://console.redhat.com/openshift). -For deploy an OSD cluster in GCP using existing Virtual Private Cloud (VPC) you need to implement some prerequisites that you must create before starting the OpenShift Dedicated installation though the OCM. +The guide will show all the steps to create all the networking prerequisites in GCP and then installing the OSD Cluster in GCP. + +> **Tip** The official documentation for installing a OSD cluster in GCP can be found [here](https://docs.openshift.com/dedicated/osd_cluster_create/creating-a-gcp-cluster.html). ## Prerequisites @@ -21,18 +23,14 @@ For deploy an OSD cluster in GCP using existing Virtual Private Cloud (VPC) you NOTE: Also the GCloud Shell can be used, and have the gcloud cli among other tools preinstalled. ## Generate GCP VPC and Subnets -This is a diagram showing the GCP infra prerequisites that are needed for the OSD installation: - -![GCP Prereqs](../images/osd-prereqs.png) -To deploy the GCP VPC and subnets among other prerequisites for install the OSD in GCP using the preexisting VPCs you have two options: +For deploy an OSD cluster in GCP using existing Virtual Private Cloud (VPC) you need to implement some prerequisites that you must create before starting the OpenShift Dedicated installation though the OCM. -* **Option 1** - GCloud CLI -* **Option 2** - Terraform Automation +This is a diagram showing the GCP infra prerequisites that are needed for the OSD installation: -Please select one of these two options and proceed with the OSD install steps. + ![GCP VPC and Subnets](../images/osd-prereqs.png) -### Option 1 - Generate OSD VPC and Subnets using GCloud CLI +You can use the gcloud CLI, to deploy the GCP VPC and subnets among other prerequisites for install the OSD in GCP. As mentioned before, for deploy OSD in GCP using existing GCP VPC, you need to provide and create beforehand a GCP VPC and two subnets (one for the masters and another for the workers nodes). @@ -91,7 +89,8 @@ NOTE: we need to create the mode custom for the VPC network, because the auto mo --project=$PROJECT_NAME --network=$OSD_VPC --region=$REGION ``` - ![GCP Routers](../images/osd-gcp2.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="350" } + ![GCP Routers](../images/osd-gcp2.png) + 7. Then, we will deploy two [GCP Cloud NATs](https://cloud.google.com/nat/docs/set-up-manage-network-address-translation#gcloud) and attach them within the GCP Router: @@ -107,7 +106,7 @@ NOTE: we need to create the mode custom for the VPC network, because the auto mo --nat-custom-subnet-ip-ranges=$MASTER_SUBNET ``` - ![GCP Nat Master](../images/osd-gcp3.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="350" } + ![GCP Nat Master](../images/osd-gcp3.png) * Generate the GCP Cloud NAT for the Worker Subnets: @@ -121,36 +120,13 @@ NOTE: we need to create the mode custom for the VPC network, because the auto mo --nat-custom-subnet-ip-ranges=$WORKER_SUBNET ``` - ![GCP Nat Worker](../images/osd-gcp4.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="350" } + ![GCP Nat Worker](../images/osd-gcp4.png) 8. As you can check the Cloud NATs GW are attached now to the Cloud Router: - ![GCP Nat Master](../images/osd-gcp5.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="350" } - -### Option 2 - Deploy OSD VPC and Subnets using Terraform - -You can use also [automation code in Terraform](https://github.com/rh-mobb/tf-osd-gcp) to deploy all the GCP infrastructure required to deploy the OSD in preexistent VPCs. + ![GCP Nat Master](../images/osd-gcp5.png) -* Clone the tf-osd-gcp repository: - -```bash -git clone https://github.com/rh-mobb/tf-osd-gcp.git -cd tf-osd-gcp -``` - -* Copy and modify the tfvars file in order to custom to your scenario: - -```bash -cp -pr terraform.tfvars.example terraform.tfvars -``` - -* Deploy the network infrastructure in GCP needed for deploy the OSD cluster: - -```bash -make all -``` - -## Install the OSD cluster using pre-existent VPCs +## Install the OSD cluster using pre-existent VPCs using the GUI These steps are based in the [official OSD installation documentation](https://docs.openshift.com/dedicated/osd_install_access_delete_cluster/creating-a-gcp-cluster.html#osd-create-gcp-cluster-ccs_osd-creating-a-cluster-on-gcp). @@ -159,39 +135,39 @@ These steps are based in the [official OSD installation documentation](https://d 2. In the Cloud tab, click Create cluster in the Red Hat OpenShift Dedicated row. 3. Under Billing model, configure the subscription type and infrastructure type -![OSD Install](../images/osd-gcp6.png){:style="display:block; margin-left:auto; margin-right:auto"} +![OSD Install](../images/osd-gcp6.png) 4. Select Run on Google Cloud Platform. 5. Click Prerequisites to review the prerequisites for installing OpenShift Dedicated on GCP with CCS. 6. Provide your GCP service account private key in JSON format. You can either click Browse to locate and attach a JSON file or add the details in the Service account JSON field. -![OSD Install](../images/osd-gcp7.png){:style="display:block; margin-left:auto; margin-right:auto"} +![OSD Install](../images/osd-gcp7.png) 7. Validate your cloud provider account and then click Next. On the Cluster details page, provide a name for your cluster and specify the cluster details: -![OSD Install](../images/osd-gcp8.png){:style="display:block; margin-left:auto; margin-right:auto"} +![OSD Install](../images/osd-gcp8.png) > NOTE: the Region used to be installed needs to be the same as the VPC and Subnets deployed in the early step. 8. On the Default machine pool page, select a Compute node instance type and a Compute node count: -![OSD Install](../images/osd-gcp9.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="600" } +![OSD Install](../images/osd-gcp9.png) 9. In the Cluster privacy section, select **Public** endpoints and application routes for your cluster. 10. Select Install into an existing VPC to install the cluster in an existing GCP Virtual Private Cloud (VPC): -![OSD Install](../images/osd-gcp10.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="600" } +![OSD Install](../images/osd-gcp10.png) 11. Provide your Virtual Private Cloud (VPC) subnet settings, that you deployed as prerequisites in the previous section: -![OSD Install](../images/osd-gcp11.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="600" } +![OSD Install](../images/osd-gcp11.png) 12. In the CIDR ranges dialog, configure custom classless inter-domain routing (CIDR) ranges or use the defaults that are provided: -![OSD Install](../images/osd-gcp12.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="600" } +![OSD Install](../images/osd-gcp12.png) 13. On the Cluster update strategy page, configure your update preferences. 14. Review the summary of your selections and click Create cluster to start the cluster installation. Check that the **Install into Existing VPC** is enabled and the VPC and Subnets are properly selected and defined: -![OSD Install](../images/osd-gcp13.png){:style="display:block; margin-left:auto; margin-right:auto"}{: width="600" } +![OSD Install](../images/osd-gcp13.png) ## Cleanup @@ -199,10 +175,7 @@ Deleting a ROSA cluster consists of two parts: 1. Deleting the OSD cluster can be done using the OCM console described in the [official OSD docs](https://docs.openshift.com/dedicated/osd_install_access_delete_cluster/creating-a-gcp-cluster.html). -2. Deleting the GCP infrastructure resources (VPC, Subnets, Cloud NAT, Cloud Router). -Depending of which option you selected you must perform: - -3. **Option 1**: Delete GCP resources using GCloud CLI: +2. Deleting the GCP infrastructure resources (VPC, Subnets, Cloud NAT, Cloud Router): ```sh gcloud compute routers nats delete $NAT_WORKER \ @@ -218,9 +191,3 @@ Depending of which option you selected you must perform: gcloud compute networks delete $OSD_VPC --quiet ``` - -4. **Option 2**: Delete GCP resources using Terraform: - - ```sh - make destroy - ```