diff --git a/docs/howto/kubernetes/gardener/assets/garhiber-01.png b/docs/howto/kubernetes/gardener/assets/garhiber-01.png index 382afcf02..f1a6f1ee8 100644 Binary files a/docs/howto/kubernetes/gardener/assets/garhiber-01.png and b/docs/howto/kubernetes/gardener/assets/garhiber-01.png differ diff --git a/docs/howto/kubernetes/gardener/assets/garhiber-02.png b/docs/howto/kubernetes/gardener/assets/garhiber-02.png index 4f0281999..60bff9b82 100644 Binary files a/docs/howto/kubernetes/gardener/assets/garhiber-02.png and b/docs/howto/kubernetes/gardener/assets/garhiber-02.png differ diff --git a/docs/howto/kubernetes/gardener/assets/garhiber-03.png b/docs/howto/kubernetes/gardener/assets/garhiber-03.png index 26ec6554f..35c25f6ae 100644 Binary files a/docs/howto/kubernetes/gardener/assets/garhiber-03.png and b/docs/howto/kubernetes/gardener/assets/garhiber-03.png differ diff --git a/docs/howto/kubernetes/gardener/assets/garhiber-04.png b/docs/howto/kubernetes/gardener/assets/garhiber-04.png index 307149756..6cf603993 100644 Binary files a/docs/howto/kubernetes/gardener/assets/garhiber-04.png and b/docs/howto/kubernetes/gardener/assets/garhiber-04.png differ diff --git a/docs/howto/kubernetes/gardener/assets/garhiber-05.png b/docs/howto/kubernetes/gardener/assets/garhiber-05.png index fbdbf240e..d8a911c7f 100644 Binary files a/docs/howto/kubernetes/gardener/assets/garhiber-05.png and b/docs/howto/kubernetes/gardener/assets/garhiber-05.png differ diff --git a/docs/howto/kubernetes/gardener/assets/garhiber-06.png b/docs/howto/kubernetes/gardener/assets/garhiber-06.png index fd7297686..0bfc4941c 100644 Binary files a/docs/howto/kubernetes/gardener/assets/garhiber-06.png and b/docs/howto/kubernetes/gardener/assets/garhiber-06.png differ diff --git a/docs/howto/kubernetes/gardener/assets/garhiber-07.png b/docs/howto/kubernetes/gardener/assets/garhiber-07.png index b9f3986a7..35ea967f7 100644 Binary files a/docs/howto/kubernetes/gardener/assets/garhiber-07.png and b/docs/howto/kubernetes/gardener/assets/garhiber-07.png differ diff --git a/docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md b/docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md index ee1825f1d..0caec63b9 100644 --- a/docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md +++ b/docs/howto/kubernetes/gardener/hibernate-shoot-cluster.md @@ -3,69 +3,58 @@ description: How to hibernate a Gardener-based Kubernetes cluster --- # Hibernating a 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. +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. ## Prerequisites -We assume you have already used {{brand_container_orchestration}} to spin up a -Kubernetes cluster, which is now humming away. If you've never done -this before, please feel free to [follow this -guide](create-shoot-cluster.md). +We assume you have already used {{brand_container_orchestration}} to spin up a Kubernetes cluster, which is now humming away. +If you've never done this before, please feel free to [follow this guide](create-shoot-cluster.md). ## Hibernating a cluster -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 the corresponding row for a detailed view of the various cluster -characteristics. Go to the *Status* tab and check if hibernation is -possible. +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. +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.27, the latest supported at the time of this writing, and hibernation is indeed possible. ![{{k8s_management_service}} cluster status](assets/garhiber-01.png) -If hibernation is indeed possible, this will be reflected in the -*Constraints* section. To go ahead and actually hibernate the cluster, -click the orange three-dot icon at the right-hand side of the cluster -row, and from the pop-up menu that appears, select *Hibernate Cluster*. +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. +From the pop-up menu that appears, select *Hibernate Cluster*. ![Hibernate cluster](assets/garhiber-02.png) -A big pop-up window will appear, asking you to confirm the action. +A big pop-up window labeled *About to hibernate a gardener shoot* appears, asking you to confirm the action. Click the red button labeled *Yes, Hibernate*. ![Confirm cluster hibernation](assets/garhiber-03.png) -After a minute or two, the cluster will be in a hibernated state. This -fact will be indicated by the white-square-in-red-circle icon, at the -left-hand side of the cluster row. +After a minute or two, the cluster will be in a hibernated state. +This fact will be indicated by the red :material-stop-circle: icon, at the left-hand side of the cluster row. ![Cluster in hibernation](assets/garhiber-04.png) -At this point, 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 list the cluster nodes, e.g., via `kubectl`, will fail. ## Waking up a cluster in hibernation -To wake up a cluster in hibernation, click the orange three-dot icon -at the right-hand side of its row. From the pop-up menu that appears, -select *Wake up Cluster*. +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/garhiber-05.png) -A big pop-up window will appear, asking you to confirm that you want -to wake the cluster. Go ahead and click the red *Yes, Wakeup* button. +A big pop-up window labeled *About to wakeup a gardener shoot* appears, asking you to confirm that you want to wake the cluster. +Go ahead and click the red *Yes, Wakeup* button. ![Confirm cluster wake-up](assets/garhiber-06.png) -After a couple of minutes, the cluster will be fully awake. The fact -will be indicated by the white-tick-in-green-circle icon, at the -left-hand side of the cluster row. +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. ![Cluster awake](assets/garhiber-07.png) -From that time on, the cluster will be accessible and fully operational again. +From that time on, the cluster will be fully operational and accessible again.