From 79d344e481ea95a9d6bf6851dbb8776b2d6d3cbe Mon Sep 17 00:00:00 2001 From: Mykhailo Kuznietsov Date: Mon, 9 Sep 2024 16:55:56 +0300 Subject: [PATCH 1/2] feat: update autoscaler documentation Signed-off-by: Mykhailo Kuznietsov --- .../pages/configuring-machine-autoscaling.adoc | 3 --- 1 file changed, 3 deletions(-) diff --git a/modules/administration-guide/pages/configuring-machine-autoscaling.adoc b/modules/administration-guide/pages/configuring-machine-autoscaling.adoc index a4a329e539..9afe0a88a6 100644 --- a/modules/administration-guide/pages/configuring-machine-autoscaling.adoc +++ b/modules/administration-guide/pages/configuring-machine-autoscaling.adoc @@ -27,11 +27,8 @@ You need to make additional configurations to the {prod-short} installation to e spec: devEnvironments: startTimeoutSeconds: 600 <1> - ignoredUnrecoverableEvents: <2> - - FailedScheduling ---- <1> Set to at least 600 seconds to allow time for a new node to be provisioned during workspace startup. -<2> Ignore the `FailedScheduling` event to allow workspace startup to continue when a new node is provisioned. == When the autoscaler removes a node To prevent workspace pods from being evicted when the autoscaler needs to remove a node, add the `"cluster-autoscaler.kubernetes.io/safe-to-evict": "false"` annotation to every workspace pod. From 33bf5d1c947cafbbe22846ed616ff178cd5bea15 Mon Sep 17 00:00:00 2001 From: Mykhailo Kuznietsov Date: Wed, 11 Sep 2024 16:41:26 +0300 Subject: [PATCH 2/2] fixup! feat: update autoscaler documentation --- .../pages/configuring-machine-autoscaling.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/modules/administration-guide/pages/configuring-machine-autoscaling.adoc b/modules/administration-guide/pages/configuring-machine-autoscaling.adoc index 9afe0a88a6..53f3238fe5 100644 --- a/modules/administration-guide/pages/configuring-machine-autoscaling.adoc +++ b/modules/administration-guide/pages/configuring-machine-autoscaling.adoc @@ -27,8 +27,11 @@ You need to make additional configurations to the {prod-short} installation to e spec: devEnvironments: startTimeoutSeconds: 600 <1> + ignoredUnrecoverableEvents: <2> + - FailedScheduling ---- <1> Set to at least 600 seconds to allow time for a new node to be provisioned during workspace startup. +<2> Ignore the `FailedScheduling` event to allow workspace startup to continue when a new node is provisioned. This setting is enabled by default. == When the autoscaler removes a node To prevent workspace pods from being evicted when the autoscaler needs to remove a node, add the `"cluster-autoscaler.kubernetes.io/safe-to-evict": "false"` annotation to every workspace pod.