Uninstalling a cluster on GCP - Installing on GCP | Installing

Removing a cluster that uses installer-provisioned infrastructure
Deleting GCP resources with the Cloud Credential Operator utility

You can remove a cluster that you deployed to Google Cloud Platform (GCP).

Removing a cluster that uses installer-provisioned infrastructure

You can remove a cluster that uses installer-provisioned infrastructure from your cloud.

After uninstallation, check your cloud provider for any resources not removed properly, especially with User Provisioned Infrastructure (UPI) clusters. There might be resources that the installer did not create or that the installer is unable to access. For example, some Google Cloud resources require IAM permissions in shared VPC host projects, or there might be unused health checks that must be deleted.

Prerequisites

You have a copy of the installation program that you used to deploy the cluster.
You have the files that the installation program generated when you created your cluster.

Procedure

From the directory that contains the installation program on the computer that you used to install the cluster, run the following command:
```
$ ./openshift-install destroy cluster \
--dir <installation_directory> --log-level info  (1) (2)
```
1 For <installation_directory>, specify the path to the directory that you stored the installation files in.

2 To view different details, specify warn, debug, or error instead of info.

You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster.
Optional: Delete the <installation_directory> directory and the OKD installation program.

Deleting GCP resources with the Cloud Credential Operator utility

To clean up resources after uninstalling an OKD cluster with the Cloud Credential Operator (CCO) in manual mode with GCP Workload Identity, you can use the CCO utility (ccoctl) to remove the GCP resources that ccoctl created during installation.

Prerequisites

Extract and prepare the ccoctl binary.
Install an OKD cluster with the CCO in manual mode with GCP Workload Identity.

Procedure

Obtain the OKD release image by running the following command:

$ RELEASE_IMAGE=$(./openshift-install version | awk '/release image/ {print $3}')

Extract the list of CredentialsRequest custom resources (CRs) from the OKD release image by running the following command:
```
$ oc adm release extract --credentials-requests \
  --cloud=gcp \
  --to=<path_to_directory_with_list_of_credentials_requests>/credrequests \ (1)
  $RELEASE_IMAGE
```
1 credrequests is the directory where the list of CredentialsRequest objects is stored. This command creates the directory if it does not exist.
Delete the GCP resources that ccoctl created:
```
$ ccoctl gcp delete \
  --name=<name> \ (1)
  --project=<gcp_project_id> \ (2)
  --credentials-requests-dir=<path_to_directory_with_list_of_credentials_requests>/credrequests
```
1 <name> matches the name that was originally used to create and tag the cloud resources.

2 <gcp_project_id> is the GCP project ID in which to delete cloud resources.

Verification

To verify that the resources are deleted, query GCP. For more information, refer to GCP documentation.

1	For `<installation_directory>`, specify the path to the directory that you stored the installation files in.
2	To view different details, specify `warn`, `debug`, or `error` instead of `info`.

1	`<name>` matches the name that was originally used to create and tag the cloud resources.
2	`<gcp_project_id>` is the GCP project ID in which to delete cloud resources.