1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/installation-aws-delete-cluster.adoc
2025-12-16 16:59:59 +00:00

61 lines
2.2 KiB
Plaintext

// Module included in the following assemblies:
//
// * installing/installing_aws/uninstalling-cluster-aws.adoc
:_mod-docs-content-type: PROCEDURE
[id="installation-aws-delete-cluster"]
= Deleting a cluster with a configured {aws-short} Local Zone infrastructure
[role="_abstract"]
After you install a cluster on {aws-first} into an existing Virtual Private Cloud (VPC), and you set subnets for each Local Zone location, you can delete the cluster and any {aws-short} 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
. Change to the directory that contains the stored installation program, and delete the cluster by using the `destroy cluster` command:
+
[source,terminal]
----
$ ./openshift-install destroy cluster --dir <installation_directory> \
--log-level=debug
----
+
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`.
. Delete the CloudFormation stack for the Local Zone subnet:
+
[source,terminal]
----
$ aws cloudformation delete-stack --stack-name <local_zone_stack_name>
----
. Delete the stack of resources that represent the VPC:
+
[source,terminal]
----
$ aws cloudformation delete-stack --stack-name <vpc_stack_name>
----
.Verification
* Check that you removed the stack resources by issuing the following commands in the {aws-short} CLI. The AWS CLI outputs that no template component exists.
+
[source,terminal]
----
$ aws cloudformation describe-stacks --stack-name <local_zone_stack_name>
----
+
[source,terminal]
----
$ aws cloudformation describe-stacks --stack-name <vpc_stack_name>
----