Skip to main content

Hibernate and Wake-up

Production clusters typically run 24/7, but dev, test, staging, and demo clusters don't need to. Scaling those down when idle saves cost — the Hibernate feature automates that scale-down instead of doing it manually.

When you hibernate a cluster:

  1. Worker Nodes (instances) are deleted.
  2. Pods move to Pending status.
  3. Services are preserved.
  4. Stateful storage (PVCs, etc.) and etcd state are preserved.

Wake-up reverses Hibernate, restoring the cluster to its pre-hibernation state.

Hibernate a cluster​

  1. From the menu, select Kubernetes to open Kubernetes Management.

    Kubernetes Management page in the left menu

  2. Select Hibernate to start the process.

    Hibernate button on the cluster page

  3. Enter the cluster name to confirm.

    Cluster name confirmation dialog for Hibernate

The cluster status changes to Hibernating (Running) while the process runs.

Cluster status showing Hibernating (Running)

Once complete, the status changes to Succeeded (Hibernated).

Cluster status showing Succeeded (Hibernated)

Wake up a cluster​

For a cluster showing Succeeded (Hibernated), use Wake-up to restore it.

  1. From the menu, select Kubernetes to open Kubernetes Management.

    Kubernetes Management page in the left menu

  2. Select Wakeup to start the process.

    Wakeup button on the cluster page

  3. Enter the cluster name to confirm.

    Cluster name confirmation dialog for Wakeup

The cluster status changes to Processing (Running) while the process runs.

Cluster status showing Processing (Running)

Once complete, the status changes to Succeeded (Running).

Cluster status showing Succeeded (Running)

note

Before hibernating, make sure every Pod is Running and other resources are healthy (LoadBalancer Services, ingress, Persistent Volumes, secrets, ConfigMaps, and so on). Deployments applied to a hibernated cluster stay Pending until you wake it up.