Lifecycle
Pause, resume, and delete managed clusters — and how connections and backups are handled.
Manage a cluster's lifecycle from its header actions. All lifecycle operations require the appropriate permission (see RBAC).
Pause & resume
Pausing a running cluster stops every node and closes its connections. Storage, backups, and credentials are kept; resuming brings the cluster back with the same data. Pause and resume are applied by the operator — if an upgrade or failover is in flight, the pause takes effect once it finishes.
While paused, the cluster cannot be connected to or edited until you resume it.
Delete
Deleting a cluster tears down its nodes. A confirmation dialog offers Keep backups for restore later (checked by default) — its backup data is retained after the cluster is gone. Restoring a deleted cluster from retained backups is not supported yet; see Backups & restore.
A cluster's connections are always removed with it — this cascade is enforced and cannot be toggled off. Losing backups (by unchecking "keep backups") is irreversible.
If a deletion terminally fails, the cluster shows a failure banner with a Retry deletion action.