Manage and delete a cluster
This guide covers common management tasks for Slurm and Kubernetes clusters after creation: checking status, updating details, reconnecting on-premises agents, and deleting a cluster.
Prerequisites
- An existing cluster (see Create a Slurm cluster or Create a Kubernetes cluster)
Check cluster status
- Click Clusters in the left sidebar and select the cluster type tab.
- The list shows each cluster with a status badge:
| Status | Meaning |
|---|---|
| preparing | Provisioning in progress |
| ready | Healthy and accepting workloads |
| failed | Provisioning or health check failed |
| destroying | Teardown in progress |
- Click a cluster name to open the detail page. The Status Details section shows timestamps and error messages for the current state.
Update cluster details
- Open the cluster detail page.
- Click
Editto modify the cluster name or description. - Click
Save.
Reconnect an on-premises agent
If an on-premises cluster shows a stale or disconnected status:
- Open the cluster detail page.
- Click
Reconnectin the actions menu. - Verify the agent process is running on your infrastructure. Check the agent logs for connectivity errors.
If the agent cannot reach Vantage, confirm outbound HTTPS (port 443) is open from your infrastructure.
Delete a cluster
- Open the cluster detail page.
- Click
Deletein the actions menu. - Confirm the deletion in the dialog.
Deleting a cluster is permanent. All running jobs are cancelled, all compute resources are deprovisioned, and any associated storage may be removed depending on the provider. Active clusters incur billing until deleted.
For cloud clusters (AWS, Azure, GCP), deletion triggers infrastructure teardown which may take several minutes. The cluster status changes to destroying until complete.
What to do when a cluster fails
If a cluster is stuck in failed status:
- Check the Status Details section on the detail page for error messages.
- Verify your cloud account credentials are valid (see Manage cloud accounts).
- See Troubleshoot clusters for common failure patterns.