Destroying a Cluster
Pre-requisites
Before destroying a cluster, ensure the following:
- No active environments: All environments deployed on the cluster must be deleted first. Atmosly will block cluster destruction if active environments exist.
- Review dependent resources: Any user-managed node groups, add-ons, and Helm chart deployments will be destroyed along with the cluster.
Destroy Workflow
Atmosly-Provisioned Clusters
- Navigate to the Cluster List page.
- Click the three dots (...) next to the cluster you want to destroy.
- Click Destroy.
- Confirm the destruction.
The destruction process follows these steps:
- Add-on removal
- Node group deletion
- Infrastructure teardown
- Resource cleanup and verification
- Final status: Destroyed
Imported Clusters
For clusters imported via cloud account or token:
- Atmosly removes the health monitoring application (Argo application).
- Checks for active environments (must be deleted first).
- For AWS/GCP imported clusters: cleans up any Atmosly-deployed add-ons and resources.
- Removes the cluster record from Atmosly.
Destroying an imported cluster in Atmosly does not destroy the actual cluster in your cloud account. It only removes it from Atmosly management.
Destroy Status
| Status | Description |
|---|---|
| Destroying | Cluster and its resources are being removed |
| Destroyed | Cluster has been successfully removed |
| Destroy Failed | Cluster destruction failed — review the logs for details |
Monitoring Destruction
You can review the deletion logs while the cluster is being destroyed. Navigate to the cluster's Logs section to track the progress of resource cleanup.
Hard Delete
After a cluster reaches Destroyed status, a hard delete option is available to permanently remove the cluster record from Atmosly. This is useful for cleaning up destroyed clusters from your cluster list.
Cluster destruction is irreversible. All user-managed node groups, add-ons, and associated data will be permanently lost.