Change, take offline, delete

Change the configuration

On the cluster page, Change the configuration lets you change the criticality, machine management (AutoPilot or fixed machines), the machines and the account.

• The hosting provider and the region don’t change. To move, create another cluster and attach your projects to it.
• The summary compares today’s planned price with the price after the change.
• You can’t change a cluster while it’s deploying or shutting down: wait until it’s done.

Apply changes records the change in a plan under your name, approves it and runs it straight away: the activity log keeps track of who changed what. The cluster is then redeployed with this configuration; progress shows on its page.

To have someone else approve it first, choose Prepare for review: the plan waits in Plans.

Take offline

In the cluster menu, choose to take it offline.

• The machines are released one by one and no longer cost anything.
• All the cluster’s projects go offline.
• IP addresses and volumes that are kept are still billed; the cluster page shows the amount.
• The configuration is kept.

Databases lose their data

When the cluster goes offline, the databases of the hosted projects lose their data. First set their Restore from to This service itself: see Backups and restore.

Bring back online

Bring back online restarts the cluster with its configuration. The console shows the estimated monthly cost; billing resumes as soon as the machines run.

• Hosted projects stay offline: deploy them afterwards.
• A database starts from its latest backup only if its restore source is set to itself; otherwise, it starts empty.
• If the configuration no longer meets the current rules (a budget below the minimum, for example), the console asks you to change it first.

Delete

Only when offline: take the cluster offline first. The cluster and its configuration are deleted; this is permanent.

Rename

Rename cluster: 30 characters at most. Only the name changes.