Skip to main content

Manage and delete a cluster

Rename, check status, reconnect, and delete Slurm and Kubernetes clusters.

Manage and delete a cluster

Check status, update details, reconnect on-premises agents, and delete clusters.

TimeAbout 2 minutes per operation
You will needAn existing Slurm or Kubernetes cluster
OutcomeCluster configuration maintained as needed

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.

Check cluster status

Open the cluster list

Click Clusters in the left sidebar and select the cluster type tab.

Review the status badge

The list shows each cluster with a status badge:

StatusMeaning
preparingProvisioning in progress
readyHealthy and accepting workloads
failedProvisioning or health check failed
destroyingTeardown in progress

View status details

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

Open the cluster detail page.

Edit the cluster

Click Edit to modify the cluster name or description.

Save your changes

Click Save.

Success looks like this: the command is accepted, and subsequent uvx v8x cluster get calls reflect the updated configuration or state.

Reconnect an on-premises agent

If an on-premises cluster shows a stale or disconnected status:

Open the cluster detail page

Open the cluster detail page.

Reconnect

Click Reconnect in the actions menu.

Verify the agent

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

Open the cluster detail page.

Delete

Click Delete in the actions menu.

Confirm

Confirm the deletion in the dialog.

warning

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 error details

Check the Status Details section on the detail page for error messages.

Verify credentials

Verify your cloud account credentials are valid (see Manage cloud accounts).

Troubleshoot

See Troubleshoot clusters for common failure patterns.

Ask AI
Ask a question about Vantage Compute...