diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-01.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-01.png index 956c6e262..535fd32dd 100644 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-01.png and b/docs/howto/kubernetes/gardener/assets/shoot-hiber-01.png differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-02.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-02.png index 24b85b802..4eea65d0f 100644 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-02.png and b/docs/howto/kubernetes/gardener/assets/shoot-hiber-02.png differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-03.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-03.png index a4173d8cb..9a5c5b4b0 100644 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-03.png and b/docs/howto/kubernetes/gardener/assets/shoot-hiber-03.png differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-04.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-04.png index 10601c7a5..ffbfc3352 100644 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-04.png and b/docs/howto/kubernetes/gardener/assets/shoot-hiber-04.png differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-05.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-05.png index 9c01c2f31..514583282 100644 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-05.png and b/docs/howto/kubernetes/gardener/assets/shoot-hiber-05.png differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-06.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-06.png deleted file mode 100644 index dcbecb6c6..000000000 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-06.png and /dev/null differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-07.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-07.png deleted file mode 100644 index bcd3a43a4..000000000 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-07.png and /dev/null differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-08.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-08.png deleted file mode 100644 index a9ecb307b..000000000 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-08.png and /dev/null differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-hiber-09.png b/docs/howto/kubernetes/gardener/assets/shoot-hiber-09.png deleted file mode 100644 index a982b6bb0..000000000 Binary files a/docs/howto/kubernetes/gardener/assets/shoot-hiber-09.png and /dev/null differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-wakeup-01.png b/docs/howto/kubernetes/gardener/assets/shoot-wakeup-01.png new file mode 100644 index 000000000..1e1be22a6 Binary files /dev/null and b/docs/howto/kubernetes/gardener/assets/shoot-wakeup-01.png differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-wakeup-02.png b/docs/howto/kubernetes/gardener/assets/shoot-wakeup-02.png new file mode 100644 index 000000000..76a6c7670 Binary files /dev/null and b/docs/howto/kubernetes/gardener/assets/shoot-wakeup-02.png differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-wakeup-03.png b/docs/howto/kubernetes/gardener/assets/shoot-wakeup-03.png new file mode 100644 index 000000000..8d75b9a2f Binary files /dev/null and b/docs/howto/kubernetes/gardener/assets/shoot-wakeup-03.png differ diff --git a/docs/howto/kubernetes/gardener/assets/shoot-wakeup-04.png b/docs/howto/kubernetes/gardener/assets/shoot-wakeup-04.png new file mode 100644 index 000000000..92a0db1e2 Binary files /dev/null and b/docs/howto/kubernetes/gardener/assets/shoot-wakeup-04.png differ diff --git a/docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md b/docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md index f2a5eeccd..f7acced00 100644 --- a/docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md +++ b/docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md @@ -5,7 +5,7 @@ description: How to hibernate a Gardener-based Kubernetes cluster There will be times when you won't be using your {{k8s_management_service}}-based cluster much, if at all. To save on costs, you can put the whole cluster in hibernation. -If you do, then from that time on (and until you wake the cluster again), you will be paying *less* for the cluster. +If you do, then from that time on and until you wake up the cluster again, you will be paying *less* for it. ## Prerequisites @@ -16,14 +16,14 @@ If you've never done this before, please feel free to [follow this guide](create Fire up your favorite web browser and navigate to . Make sure the vertical pane at the left-hand side of the page is in full view, then choose *Containers → [{{k8s_management_service}}](https://{{gui_domain}}/containers/gardener)*. -In the main pane, you will see your {{k8s_management_service}} cluster. -Click anywhere on its row for a detailed view of the various cluster characteristics. +You will see your {{k8s_management_service}} cluster in the main pane. +Click on its row for a detailed view of the various cluster characteristics. Bring up the *Status* tab and, in the *Constraints* section, check whether hibernation is possible. -In the example below we have a shoot cluster based on Kubernetes 1.29, the latest supported at the time of this writing, and hibernation is indeed possible. +For the shoot cluster in the example below, it is indeed possible. ![{{k8s_management_service}} cluster status](assets/shoot-hiber-01.png) -To go ahead and actually hibernate the cluster, click the orange :material-dots-horizontal-circle: icon at the right-hand side of the cluster row. +To hibernate the cluster, click the orange :material-dots-horizontal-circle: icon at the right-hand side of the cluster row. From the pop-up menu that appears, select *Hibernate Cluster*. ![Hibernate cluster](assets/shoot-hiber-02.png) @@ -43,28 +43,28 @@ This fact will be indicated by the red :material-stop-circle: icon, again at the ![Cluster in hibernation](assets/shoot-hiber-05.png) -From this point on, and as long as the cluster is in hibernation, any attempt to list the cluster nodes, e.g., via `kubectl`, will fail. +From this point on, and as long as the cluster is in hibernation, any attempt to access it, e.g., via `kubectl`, will fail. ## Waking up a cluster in hibernation To wake up a cluster in hibernation, click the orange :material-dots-horizontal-circle: icon at the right-hand side of its row. From the pop-up menu that appears, select *Wake up Cluster*. -![Wake up cluster](assets/shoot-hiber-06.png) +![Wake up cluster](assets/shoot-wakeup-01.png) -A big pop-up window labeled *About to wakeup a gardener shoot* appears, asking you to confirm that you want to wake the cluster. +A big pop-up window labeled *About to wakeup a gardener shoot* appears, asking you to confirm that you want to wake up the cluster. Go ahead and click the red *Yes, Wakeup* button. -![Confirm cluster wake-up](assets/shoot-hiber-07.png) +![Confirm cluster wake-up](assets/shoot-wakeup-02.png) The cluster will start waking up. Again, the animated icon at the left-hand side of the cluster row marks the progress. -![Cluster is awaking](assets/shoot-hiber-08.png) +![Cluster is awaking](assets/shoot-wakeup-03.png) After a couple of minutes, the cluster will be fully awake. -The fact will be indicated by the green :material-check-circle: icon, at the left-hand side of the cluster row. +The fact will be indicated by the green :material-check-circle: icon at the left-hand side of the cluster row. -![Cluster awake](assets/shoot-hiber-09.png) +![Cluster awake](assets/shoot-wakeup-04.png) -From that time on, the cluster will be fully operational and accessible again. +From then on, the cluster will be fully operational and accessible again.