Manage a cluster
Change a registered cluster, issue a join token, revoke an agent, or remove a cluster from the platform.
Requires: kernel/clusters/write
Every change on this page needs kernel/clusters/write at the platform root, which only Platform
Owner holds. Open Settings → Platform Settings and the Clusters tab.
Edit a cluster
Choose the pencil on the cluster's row. Edit cluster changes the Name, Region, how the API server is reached, and whether the cluster Accepts inbound links (Crosslink hub eligible). Leave CA certificate blank to keep the stored one. Choose Save changes.
The platform opens new connections with the new values; nothing is re-deployed.
Note
A cluster registered as Agent cannot be switched to an external Direct API server in the edit sheet: the API URL and certificate are saved, but the cluster stays an Agent cluster, so they have no effect. Switching an Agent cluster to the cluster the platform runs in does take effect.
Issue a join token
For an Agent cluster, the edit sheet has an Agent section with Issue join token. It issues a new single-use token, valid for an hour, and shows it once. See Agent clusters for why a token cannot be used to enrol an agent yet.
Revoke an agent
Revoke agent, in the same Agent section, asks for confirmation and then:
- marks the cluster Revoked;
- deletes the agent's identity, so it can no longer sign in;
- drops the agent's live connection.
From then on the platform refuses the agent's connections. The cluster stays registered, and stays Revoked until an agent enrols with a join token — which includes a token issued before the revocation that has not been used or expired yet.
Delete a cluster
Choose the bin on the cluster's row and confirm Delete cluster?.
Deleting removes the cluster's registration and nothing else:
- Resources already running there keep running — nothing in the cluster is touched — but the platform can no longer reach them, so they cannot be changed or deleted from Stackship.
- No new resource can be placed on the cluster.
- Boundary projections onto the cluster, its join tokens, and an agent's identity are not removed.
Delete the resources placed on a cluster before you delete the cluster.