Este conteúdo não está disponível no idioma selecionado.
Chapter 15. Uninstalling a cluster on Google Cloud
You can remove a cluster that you deployed to Google Cloud.
15.1. Removing a cluster that uses installer-provisioned infrastructure Copiar o linkLink copiado para a área de transferência!
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
$ ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info1 2 Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteYou must specify the directory that contains the cluster definition files for your cluster. The installation program requires the
metadata.jsonfile in this directory to delete the cluster.-
Optional: Delete the
<installation_directory>directory and the OpenShift Container Platform installation program.
15.2. Deleting Google Cloud resources with the Cloud Credential Operator utility Copiar o linkLink copiado para a área de transferência!
After uninstalling an OpenShift Container Platform cluster that uses short-term credentials managed outside the cluster, you can use the CCO utility (ccoctl) to remove the Google Cloud resources that ccoctl created during installation.
Prerequisites
-
Extract and prepare the
ccoctlbinary. - Uninstall an OpenShift Container Platform cluster on Google Cloud that uses short-term credentials.
Procedure
Set a
$RELEASE_IMAGEvariable with the release image from your installation file by running the following command:RELEASE_IMAGE=$(./openshift-install version | awk '/release image/ {print $3}')$ RELEASE_IMAGE=$(./openshift-install version | awk '/release image/ {print $3}')Copy to Clipboard Copied! Toggle word wrap Toggle overflow Extract the list of
CredentialsRequestcustom resources (CRs) from the OpenShift Container Platform release image by running the following command:oc adm release extract \ --from=$RELEASE_IMAGE \ --credentials-requests \ --included \ --to=<path_to_directory_for_credentials_requests>
$ oc adm release extract \ --from=$RELEASE_IMAGE \ --credentials-requests \ --included \1 --to=<path_to_directory_for_credentials_requests>2 Copy to Clipboard Copied! Toggle word wrap Toggle overflow Delete the Google Cloud resources that
ccoctlcreated by running the following command:ccoctl gcp delete \ --name=<name> \ --project=<gcp_project_id> \ --credentials-requests-dir=<path_to_credentials_requests_directory> \ --force-delete-custom-roles
$ ccoctl gcp delete \ --name=<name> \1 --project=<gcp_project_id> \2 --credentials-requests-dir=<path_to_credentials_requests_directory> \ --force-delete-custom-roles3 Copy to Clipboard Copied! Toggle word wrap Toggle overflow - 1
<name>matches the name that was originally used to create and tag the cloud resources.- 2
<gcp_project_id>is the Google Cloud project ID in which to delete cloud resources.- 3
- Optional: This parameter deletes the custom roles that the
ccoctlutility creates during installation. Google Cloud does not permanently delete custom roles immediately. For more information, see Google Cloud documentation about deleting a custom role.
Verification
- To verify that the resources are deleted, query Google Cloud. For more information, refer to Google Cloud documentation.