What problem does it solve?
Tearing down a HyperShift HostedCluster on AWS involves removing many cloud resources (VPCs, subnets, NAT gateways, IAM roles, Route53 zones, OIDC providers), and manual cleanup is error-prone and often leaves orphaned resources that incur costs.
Core Features & Use Cases
- Full Cluster Teardown: Runs
hypershift destroy cluster aws to delete the HostedCluster, NodePools, HostedControlPlane namespace, and all AWS infrastructure.
- Comprehensive AWS Cleanup: Removes VPCs, subnets, NAT and internet gateways, route tables, security groups, DHCP options, Route53 private hosted zones, OIDC providers, IAM roles, VPC endpoints, and Elastic IPs.
- Orphaned Cluster Recovery: Provides a force-removal path for stuck HostedClusters by removing the cleanup-cloud-resources annotation.
- Use Case: After finishing an end-to-end test run, destroy the test HostedCluster
my-test-cluster in the clusters namespace so no AWS resources keep billing.
Quick Start
Ask the assistant to destroy the HostedCluster named my-test-cluster in the clusters namespace on AWS using the configured management kubeconfig and AWS credentials.