Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

Chapter 6. Uninstalling a cluster on AWS

You can remove a cluster that you deployed to Amazon Web Services (AWS).

6.1. Removing a cluster that uses installer-provisioned infrastructure
リンクのコピー

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

Note

After uninstallation, check your cloud provider for any resources that were not removed properly, especially with user-provisioned infrastructure clusters. Some resources might exist because either the installation program did not create the resource or could not access the resource.

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

  1. From the directory that has 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
    Copy to Clipboard Toggle word wrap

    where:

    <installation_directory>
    Specify the path to the directory that you stored the installation files in.
    --log-level info

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

    Note

    You must specify the directory that includes the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster.

  2. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program.

6.2. Deleting Amazon Web Services resources with the Cloud Credential Operator utility
リンクのコピー

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 Amazon Web Services resources that ccoctl created during installation.

Prerequisites

  • Extract and prepare the ccoctl binary.
  • Uninstall an OpenShift Container Platform cluster on AWS that uses short-term credentials.

Procedure

  • Delete the AWS resources that ccoctl created by running the following command: 

    $ ccoctl aws delete \
  --name=<name> \
ifdef::aws-sts
[  --region=<aws_region>]
    Copy to Clipboard Toggle word wrap

    where:

    <name>
    Matches the name that was originally used to create and tag the cloud resources.
    <aws_region>

    is the AWS region in which to delete cloud resources.

    Example output

    2021/04/08 17:50:41 Identity Provider object .well-known/openid-configuration deleted from the bucket <name>-oidc
2021/04/08 17:50:42 Identity Provider object keys.json deleted from the bucket <name>-oidc
2021/04/08 17:50:43 Identity Provider bucket <name>-oidc deleted
2021/04/08 17:51:05 Policy <name>-openshift-cloud-credential-operator-cloud-credential-o associated with IAM Role <name>-openshift-cloud-credential-operator-cloud-credential-o deleted
2021/04/08 17:51:05 IAM Role <name>-openshift-cloud-credential-operator-cloud-credential-o deleted
2021/04/08 17:51:07 Policy <name>-openshift-cluster-csi-drivers-ebs-cloud-credentials associated with IAM Role <name>-openshift-cluster-csi-drivers-ebs-cloud-credentials deleted
2021/04/08 17:51:07 IAM Role <name>-openshift-cluster-csi-drivers-ebs-cloud-credentials deleted
2021/04/08 17:51:08 Policy <name>-openshift-image-registry-installer-cloud-credentials associated with IAM Role <name>-openshift-image-registry-installer-cloud-credentials deleted
2021/04/08 17:51:08 IAM Role <name>-openshift-image-registry-installer-cloud-credentials deleted
2021/04/08 17:51:09 Policy <name>-openshift-ingress-operator-cloud-credentials associated with IAM Role <name>-openshift-ingress-operator-cloud-credentials deleted
2021/04/08 17:51:10 IAM Role <name>-openshift-ingress-operator-cloud-credentials deleted
2021/04/08 17:51:11 Policy <name>-openshift-machine-api-aws-cloud-credentials associated with IAM Role <name>-openshift-machine-api-aws-cloud-credentials deleted
2021/04/08 17:51:11 IAM Role <name>-openshift-machine-api-aws-cloud-credentials deleted
2021/04/08 17:51:39 Identity Provider with ARN arn:aws:iam::<aws_account_id>:oidc-provider/<name>-oidc.s3.<aws_region>.amazonaws.com deleted
    Copy to Clipboard Toggle word wrap

Verification

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

6.3. Deleting a cluster with a configured AWS Local Zone infrastructure
リンクのコピー

After you install a cluster on Amazon Web Services (AWS) into an existing Virtual Private Cloud (VPC), and you set subnets for each Local Zone location, you can delete the cluster and any AWS resources associated with it.

The example in the procedure assumes that you created a VPC and its subnets by using a CloudFormation template.

Prerequisites

  • You know the name of the CloudFormation stacks, <local_zone_stack_name> and <vpc_stack_name>, that were used during the creation of the network. You need the name of the stack to delete the cluster.
  • You have access rights to the directory that contains the installation files that were created by the installation program.
  • Your account includes a policy that provides you with permissions to delete the CloudFormation stack.

Procedure

  1. Change to the directory that contains the stored installation program, and delete the cluster by using the destroy cluster command: 

    $ ./openshift-install destroy cluster --dir <installation_directory> \
   --log-level=debug
    Copy to Clipboard Toggle word wrap

    where:

    <installation_directory>
    Specify the directory that stored any files created by the installation program.
    --log-level=debug
    To view different log details, specify error, info, or warn instead of debug.

  2. Delete the CloudFormation stack for the Local Zone subnet: 

    $ aws cloudformation delete-stack --stack-name <local_zone_stack_name>
    Copy to Clipboard Toggle word wrap

  3. Delete the stack of resources that represent the VPC: 

    $ aws cloudformation delete-stack --stack-name <vpc_stack_name>
    Copy to Clipboard Toggle word wrap

Verification

  • Check that you removed the stack resources by issuing the following commands in the AWS CLI. The AWS CLI outputs that no template component exists. 

    $ aws cloudformation describe-stacks --stack-name <local_zone_stack_name>
    Copy to Clipboard Toggle word wrap 
    $ aws cloudformation describe-stacks --stack-name <vpc_stack_name>
    Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2026 Red Hatトップに戻る