From 17b18c384385d82b6a94788e4a613168dd42e6c7 Mon Sep 17 00:00:00 2001 From: archups Date: Tue, 23 Jul 2024 01:48:18 +0530 Subject: [PATCH 1/2] Update cluster autoscaler addon documentation for newly added flags option Signed-off-by: archups --- .../main/guides/autoscaler-addon/_index.en.md | 40 ++++++++++++++++++- .../v1.8/guides/autoscaler-addon/_index.en.md | 40 ++++++++++++++++++- .../kkp-autoscaler/_index.en.md | 19 ++++++--- .../kkp-autoscaler/_index.en.md | 19 ++++++--- 4 files changed, 106 insertions(+), 12 deletions(-) diff --git a/content/kubeone/main/guides/autoscaler-addon/_index.en.md b/content/kubeone/main/guides/autoscaler-addon/_index.en.md index f86272dbb..038c6890e 100644 --- a/content/kubeone/main/guides/autoscaler-addon/_index.en.md +++ b/content/kubeone/main/guides/autoscaler-addon/_index.en.md @@ -46,7 +46,43 @@ addons: If you wish to change some of the properties, such as timeout for scaling up/down, you’ll need to provide the appropriate command-line flags to cluster-autoscaler. For that, you’ll need to override the cluster-autoscaler addon embedded in the KubeOne binary with your addon. -To find out how to override embedded add-ons, please check the [Addons document][embedded-addons]. For more information regarding available configuration parameters and options, please check the [Cluster Autoscaler FAQ][ca-faq]. +To find out how to override embedded add-ons, please check the [Addons document][embedded-addons]. + +If you are facing issue similar to the one described over [here][enforce-node-group-min-size] in the [Cluster Autoscaler FAQ][ca-faq], pass down the param `CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE` to the cluster autoscaler addon as shown below: + +```yaml +apiVersion: kubeone.k8c.io/v1beta2 +kind: KubeOneCluster +versions: + kubernetes: '1.29.4' ## kubernetes version +cloudProvider: ## This field is sourced automatically if terraform is used for the cluster + aws: {} +addons: + enable: true + addons: + - name: cluster-autoscaler + params: + CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE: "true" +``` + +If you are facing issue similar to the one described over [here][balance-similar-node-groups] in the [Cluster Autoscaler FAQ][ca-faq], pass down the param `CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP` to the cluster autoscaler addon as shown below: + +```yaml +apiVersion: kubeone.k8c.io/v1beta2 +kind: KubeOneCluster +versions: + kubernetes: '1.29.4' ## kubernetes version +cloudProvider: ## This field is sourced automatically if terraform is used for the cluster + aws: {} +addons: + enable: true + addons: + - name: cluster-autoscaler + params: + CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP: "true" +``` + +For more information regarding available configuration parameters and options, please check the [Cluster Autoscaler FAQ][ca-faq]. ### Step 3: Deploying Kubernetes Cluster Autoscaler @@ -212,3 +248,5 @@ That is it! You have successfully deployed Kubernetes autoscaler on the KubeOne [embedded-addons]: {{< ref "../../guides/addons/#overriding-embedded-eddons" >}} [ca-faq]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md [ca-faq-what-is]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-is-cluster-autoscaler +[enforce-node-group-min-size]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why +[balance-similar-node-groups]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler diff --git a/content/kubeone/v1.8/guides/autoscaler-addon/_index.en.md b/content/kubeone/v1.8/guides/autoscaler-addon/_index.en.md index f86272dbb..038c6890e 100644 --- a/content/kubeone/v1.8/guides/autoscaler-addon/_index.en.md +++ b/content/kubeone/v1.8/guides/autoscaler-addon/_index.en.md @@ -46,7 +46,43 @@ addons: If you wish to change some of the properties, such as timeout for scaling up/down, you’ll need to provide the appropriate command-line flags to cluster-autoscaler. For that, you’ll need to override the cluster-autoscaler addon embedded in the KubeOne binary with your addon. -To find out how to override embedded add-ons, please check the [Addons document][embedded-addons]. For more information regarding available configuration parameters and options, please check the [Cluster Autoscaler FAQ][ca-faq]. +To find out how to override embedded add-ons, please check the [Addons document][embedded-addons]. + +If you are facing issue similar to the one described over [here][enforce-node-group-min-size] in the [Cluster Autoscaler FAQ][ca-faq], pass down the param `CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE` to the cluster autoscaler addon as shown below: + +```yaml +apiVersion: kubeone.k8c.io/v1beta2 +kind: KubeOneCluster +versions: + kubernetes: '1.29.4' ## kubernetes version +cloudProvider: ## This field is sourced automatically if terraform is used for the cluster + aws: {} +addons: + enable: true + addons: + - name: cluster-autoscaler + params: + CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE: "true" +``` + +If you are facing issue similar to the one described over [here][balance-similar-node-groups] in the [Cluster Autoscaler FAQ][ca-faq], pass down the param `CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP` to the cluster autoscaler addon as shown below: + +```yaml +apiVersion: kubeone.k8c.io/v1beta2 +kind: KubeOneCluster +versions: + kubernetes: '1.29.4' ## kubernetes version +cloudProvider: ## This field is sourced automatically if terraform is used for the cluster + aws: {} +addons: + enable: true + addons: + - name: cluster-autoscaler + params: + CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP: "true" +``` + +For more information regarding available configuration parameters and options, please check the [Cluster Autoscaler FAQ][ca-faq]. ### Step 3: Deploying Kubernetes Cluster Autoscaler @@ -212,3 +248,5 @@ That is it! You have successfully deployed Kubernetes autoscaler on the KubeOne [embedded-addons]: {{< ref "../../guides/addons/#overriding-embedded-eddons" >}} [ca-faq]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md [ca-faq-what-is]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-is-cluster-autoscaler +[enforce-node-group-min-size]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why +[balance-similar-node-groups]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler diff --git a/content/kubermatic/main/tutorials-howtos/kkp-autoscaler/_index.en.md b/content/kubermatic/main/tutorials-howtos/kkp-autoscaler/_index.en.md index be0d5442c..702ba3bf7 100644 --- a/content/kubermatic/main/tutorials-howtos/kkp-autoscaler/_index.en.md +++ b/content/kubermatic/main/tutorials-howtos/kkp-autoscaler/_index.en.md @@ -8,7 +8,7 @@ This section deals with the usage of Kubernetes Cluster Autoscaler in a KKP User ## What is a Cluster Autoscaler in Kubernetes? -Kubernetes Cluster Autoscaler is a tool that automatically adjusts the size of the worker’s node up or down depending on the consumption. This means that the autoscaler, for example, automatically scale up a cluster by increasing the node count when there are not enough node resources for cluster workload scheduling and scale down when the node resources have continuously staying idle, or there are more than enough node resources available for cluster workload scheduling. In a nutshell, it is a component that automatically adjusts the size of a Kubernetes cluster so that all pods have a place to run and there are no unneeded nodes. +Kubernetes Cluster Autoscaler is a tool that automatically adjusts the size of the worker’s node up or down depending on the consumption. This means that the cluster autoscaler, for example, automatically scale up a cluster by increasing the node count when there are not enough node resources for cluster workload scheduling and scale down when the node resources have continuously staying idle, or there are more than enough node resources available for cluster workload scheduling. In a nutshell, it is a component that automatically adjusts the size of a Kubernetes cluster so that all pods have a place to run and there are no unneeded nodes. ## KKP Cluster Autoscaler Usage @@ -43,7 +43,7 @@ kube-proxy-tstvd 1/1 Running 0 21m node-local-dns-4p8jr 1/1 Running 0 21m ``` -As shown above, the autoscaler is not part of the running Kubernetes components within the namespace. +As shown above, the cluster autoscaler is not part of the running Kubernetes components within the namespace. **Step 3** @@ -82,7 +82,7 @@ coredns-666448b887-s8wv8 1/1 Running 0 36m coredns-666448b887-vldzz 1/1 Running 0 36m ``` -As shown above, the autoscaler has been provisioned and running. +As shown above, the cluster autoscaler has been provisioned and running. ## Annotating MachineDeployments for Autoscaling @@ -171,7 +171,7 @@ Metadata: …………………… ``` -As shown above, the MachineDeployment has been annotated with a minimum of 1 and a maximum of 5. Therefore, the autoscaler will consider only the annotated MachineDeployment on the cluster. +As shown above, the MachineDeployment has been annotated with a minimum of 1 and a maximum of 5. Therefore, the cluster autoscaler will consider only the annotated MachineDeployment on the cluster. ## Edit KKP Autoscaler @@ -187,7 +187,16 @@ You can delete autoscaler from where you edit it above and select delete. ![Delete Autoscaler](images/delete-autoscaler.png?classes=shadow,border "Delete Autoscaler") - Once it has been deleted, you can check the cluster to ensure that the autoscaler has been deleted using the command `kubectl get pods -n kube-system`. + Once it has been deleted, you can check the cluster to ensure that the cluster autoscaler has been deleted using the command `kubectl get pods -n kube-system`. + + +## Customize KKP Autoscaler + +You can customize the cluster autoscaler addon in order to override the cluster autoscaler deployment definition to set or pass the required flag(s) by following the instructions provided over [here](https://docs.kubermatic.com/kubermatic/v2.25/architecture/concept/kkp-concepts/addons/#custom-addons), if you are facing any of the below mentioned issues as described in the [cluster autoscaler FAQs](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md): + +* [My cluster is below minimum / above maximum number of nodes, but CA did not fix that! Why?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why) + +* [I'm running cluster with nodes in multiple zones for HA purposes. Is that supported by Cluster Autoscaler?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler) ## Summary diff --git a/content/kubermatic/v2.25/tutorials-howtos/kkp-autoscaler/_index.en.md b/content/kubermatic/v2.25/tutorials-howtos/kkp-autoscaler/_index.en.md index d9c4b5c6f..7c18f50c3 100644 --- a/content/kubermatic/v2.25/tutorials-howtos/kkp-autoscaler/_index.en.md +++ b/content/kubermatic/v2.25/tutorials-howtos/kkp-autoscaler/_index.en.md @@ -8,7 +8,7 @@ This section deals with the usage of Kubernetes Cluster Autoscaler in a KKP User ## What is a Cluster Autoscaler in Kubernetes? -Kubernetes Cluster Autoscaler is a tool that automatically adjusts the size of the worker’s node up or down depending on the consumption. This means that the autoscaler, for example, automatically scale up a cluster by increasing the node count when there are not enough node resources for cluster workload scheduling and scale down when the node resources have continuously staying idle, or there are more than enough node resources available for cluster workload scheduling. In a nutshell, it is a component that automatically adjusts the size of a Kubernetes cluster so that all pods have a place to run and there are no unneeded nodes. +Kubernetes Cluster Autoscaler is a tool that automatically adjusts the size of the worker’s node up or down depending on the consumption. This means that the cluster autoscaler, for example, automatically scale up a cluster by increasing the node count when there are not enough node resources for cluster workload scheduling and scale down when the node resources have continuously staying idle, or there are more than enough node resources available for cluster workload scheduling. In a nutshell, it is a component that automatically adjusts the size of a Kubernetes cluster so that all pods have a place to run and there are no unneeded nodes. ## KKP Cluster Autoscaler Usage @@ -43,7 +43,7 @@ kube-proxy-tstvd 1/1 Running 0 21m node-local-dns-4p8jr 1/1 Running 0 21m ``` -As shown above, the autoscaler is not part of the running Kubernetes components within the namespace. +As shown above, the cluster autoscaler is not part of the running Kubernetes components within the namespace. **Step 3** @@ -82,7 +82,7 @@ coredns-666448b887-s8wv8 1/1 Running 0 36m coredns-666448b887-vldzz 1/1 Running 0 36m ``` -As shown above, the autoscaler has been provisioned and running. +As shown above, the cluster autoscaler has been provisioned and running. ## Annotating MachineDeployments for Autoscaling @@ -171,7 +171,7 @@ Metadata: …………………… ``` -As shown above, the MachineDeployment has been annotated with a minimum of 1 and a maximum of 5. Therefore, the autoscaler will consider only the annotated MachineDeployment on the cluster. +As shown above, the MachineDeployment has been annotated with a minimum of 1 and a maximum of 5. Therefore, the cluster autoscaler will consider only the annotated MachineDeployment on the cluster. ## Edit KKP Autoscaler @@ -187,7 +187,16 @@ You can delete autoscaler from where you edit it above and select delete. ![Delete Autoscaler](/img/kubermatic/v2.25/tutorials/cluster-autoscaler/delete-autoscaler.png?classes=shadow,border "Delete Autoscaler") - Once it has been deleted, you can check the cluster to ensure that the autoscaler has been deleted using the command `kubectl get pods -n kube-system`. + Once it has been deleted, you can check the cluster to ensure that the cluster autoscaler has been deleted using the command `kubectl get pods -n kube-system`. + + +## Customize KKP Autoscaler + +You can customize the cluster autoscaler addon in order to override the cluster autoscaler deployment definition to set or pass the required flag(s) by following the instructions provided over [here](https://docs.kubermatic.com/kubermatic/v2.25/architecture/concept/kkp-concepts/addons/#custom-addons), if you are facing any of the below mentioned issues as described in the [cluster autoscaler FAQs](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md): + +* [My cluster is below minimum / above maximum number of nodes, but CA did not fix that! Why?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why) + +* [I'm running cluster with nodes in multiple zones for HA purposes. Is that supported by Cluster Autoscaler?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler) ## Summary From f30d6da2f5f3fae3a6ec2f463c852af77ec29812 Mon Sep 17 00:00:00 2001 From: archups Date: Wed, 24 Jul 2024 23:50:42 +0530 Subject: [PATCH 2/2] Updated as per review comments Signed-off-by: archups --- .../main/guides/autoscaler-addon/_index.en.md | 34 +++++++------------ .../v1.8/guides/autoscaler-addon/_index.en.md | 34 +++++++------------ .../kkp-autoscaler/_index.en.md | 6 ++-- .../kkp-autoscaler/_index.en.md | 6 ++-- 4 files changed, 30 insertions(+), 50 deletions(-) diff --git a/content/kubeone/main/guides/autoscaler-addon/_index.en.md b/content/kubeone/main/guides/autoscaler-addon/_index.en.md index 038c6890e..639d8308a 100644 --- a/content/kubeone/main/guides/autoscaler-addon/_index.en.md +++ b/content/kubeone/main/guides/autoscaler-addon/_index.en.md @@ -42,13 +42,11 @@ addons: - name: cluster-autoscaler ``` -### (Optional) Step 2: Modifying the cluster-autoscaler addon - -If you wish to change some of the properties, such as timeout for scaling up/down, you’ll need to provide the appropriate command-line flags to cluster-autoscaler. For that, you’ll need to override the cluster-autoscaler addon embedded in the KubeOne binary with your addon. +{{% notice note %}} -To find out how to override embedded add-ons, please check the [Addons document][embedded-addons]. +If you're facing an issue where your [cluster is below the minimum or above the maximum number of nodes, but the cluster-autoscaler is not fixing it][enforce-node-group-min-size], you need to pass down the `CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE` parameter to the cluster-autoscaler addon as shown below. -If you are facing issue similar to the one described over [here][enforce-node-group-min-size] in the [Cluster Autoscaler FAQ][ca-faq], pass down the param `CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE` to the cluster autoscaler addon as shown below: +If you're running a cluster with nodes in the multiple zones for the HA purposes, consider setting the `CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP` parameter to `true` as shown below. For more information about this parameter, check the [Cluster Autoscaler FAQ][balance-similar-node-groups]. ```yaml apiVersion: kubeone.k8c.io/v1beta2 @@ -62,25 +60,17 @@ addons: addons: - name: cluster-autoscaler params: + # remove the parameter which you don't need. CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE: "true" + CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP: "true" ``` +{{% /notice %}} -If you are facing issue similar to the one described over [here][balance-similar-node-groups] in the [Cluster Autoscaler FAQ][ca-faq], pass down the param `CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP` to the cluster autoscaler addon as shown below: +### (Optional) Step 2: Modifying the cluster-autoscaler addon -```yaml -apiVersion: kubeone.k8c.io/v1beta2 -kind: KubeOneCluster -versions: - kubernetes: '1.29.4' ## kubernetes version -cloudProvider: ## This field is sourced automatically if terraform is used for the cluster - aws: {} -addons: - enable: true - addons: - - name: cluster-autoscaler - params: - CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP: "true" -``` +If you wish to change some of the properties, such as timeout for scaling up/down, you’ll need to provide the appropriate command-line flags to cluster-autoscaler. For that, you’ll need to override the cluster-autoscaler addon embedded in the KubeOne binary with your addon. + +To find out how to override embedded add-ons, please check the [Addons document][embedded-addons]. For more information regarding available configuration parameters and options, please check the [Cluster Autoscaler FAQ][ca-faq]. @@ -248,5 +238,5 @@ That is it! You have successfully deployed Kubernetes autoscaler on the KubeOne [embedded-addons]: {{< ref "../../guides/addons/#overriding-embedded-eddons" >}} [ca-faq]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md [ca-faq-what-is]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-is-cluster-autoscaler -[enforce-node-group-min-size]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why -[balance-similar-node-groups]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler +[enforce-node-group-min-size]: https://github.com/kubernetes/autoscaler/blob/aff50d773e42f95baaae300f27e3b2e9cba1ea1b/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why +[balance-similar-node-groups]: https://github.com/kubernetes/autoscaler/blob/aff50d773e42f95baaae300f27e3b2e9cba1ea1b/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler diff --git a/content/kubeone/v1.8/guides/autoscaler-addon/_index.en.md b/content/kubeone/v1.8/guides/autoscaler-addon/_index.en.md index 038c6890e..639d8308a 100644 --- a/content/kubeone/v1.8/guides/autoscaler-addon/_index.en.md +++ b/content/kubeone/v1.8/guides/autoscaler-addon/_index.en.md @@ -42,13 +42,11 @@ addons: - name: cluster-autoscaler ``` -### (Optional) Step 2: Modifying the cluster-autoscaler addon - -If you wish to change some of the properties, such as timeout for scaling up/down, you’ll need to provide the appropriate command-line flags to cluster-autoscaler. For that, you’ll need to override the cluster-autoscaler addon embedded in the KubeOne binary with your addon. +{{% notice note %}} -To find out how to override embedded add-ons, please check the [Addons document][embedded-addons]. +If you're facing an issue where your [cluster is below the minimum or above the maximum number of nodes, but the cluster-autoscaler is not fixing it][enforce-node-group-min-size], you need to pass down the `CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE` parameter to the cluster-autoscaler addon as shown below. -If you are facing issue similar to the one described over [here][enforce-node-group-min-size] in the [Cluster Autoscaler FAQ][ca-faq], pass down the param `CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE` to the cluster autoscaler addon as shown below: +If you're running a cluster with nodes in the multiple zones for the HA purposes, consider setting the `CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP` parameter to `true` as shown below. For more information about this parameter, check the [Cluster Autoscaler FAQ][balance-similar-node-groups]. ```yaml apiVersion: kubeone.k8c.io/v1beta2 @@ -62,25 +60,17 @@ addons: addons: - name: cluster-autoscaler params: + # remove the parameter which you don't need. CLUSTER_AUTOSCALER_ENFORCE_NODE_GROUP_MIN_SIZE: "true" + CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP: "true" ``` +{{% /notice %}} -If you are facing issue similar to the one described over [here][balance-similar-node-groups] in the [Cluster Autoscaler FAQ][ca-faq], pass down the param `CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP` to the cluster autoscaler addon as shown below: +### (Optional) Step 2: Modifying the cluster-autoscaler addon -```yaml -apiVersion: kubeone.k8c.io/v1beta2 -kind: KubeOneCluster -versions: - kubernetes: '1.29.4' ## kubernetes version -cloudProvider: ## This field is sourced automatically if terraform is used for the cluster - aws: {} -addons: - enable: true - addons: - - name: cluster-autoscaler - params: - CLUSTER_AUTOSCALER_BALANCE_SIMILAR_NODE_GROUP: "true" -``` +If you wish to change some of the properties, such as timeout for scaling up/down, you’ll need to provide the appropriate command-line flags to cluster-autoscaler. For that, you’ll need to override the cluster-autoscaler addon embedded in the KubeOne binary with your addon. + +To find out how to override embedded add-ons, please check the [Addons document][embedded-addons]. For more information regarding available configuration parameters and options, please check the [Cluster Autoscaler FAQ][ca-faq]. @@ -248,5 +238,5 @@ That is it! You have successfully deployed Kubernetes autoscaler on the KubeOne [embedded-addons]: {{< ref "../../guides/addons/#overriding-embedded-eddons" >}} [ca-faq]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md [ca-faq-what-is]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-is-cluster-autoscaler -[enforce-node-group-min-size]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why -[balance-similar-node-groups]: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler +[enforce-node-group-min-size]: https://github.com/kubernetes/autoscaler/blob/aff50d773e42f95baaae300f27e3b2e9cba1ea1b/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why +[balance-similar-node-groups]: https://github.com/kubernetes/autoscaler/blob/aff50d773e42f95baaae300f27e3b2e9cba1ea1b/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler diff --git a/content/kubermatic/main/tutorials-howtos/kkp-autoscaler/_index.en.md b/content/kubermatic/main/tutorials-howtos/kkp-autoscaler/_index.en.md index 702ba3bf7..fe09e46da 100644 --- a/content/kubermatic/main/tutorials-howtos/kkp-autoscaler/_index.en.md +++ b/content/kubermatic/main/tutorials-howtos/kkp-autoscaler/_index.en.md @@ -192,11 +192,11 @@ You can delete autoscaler from where you edit it above and select delete. ## Customize KKP Autoscaler -You can customize the cluster autoscaler addon in order to override the cluster autoscaler deployment definition to set or pass the required flag(s) by following the instructions provided over [here](https://docs.kubermatic.com/kubermatic/v2.25/architecture/concept/kkp-concepts/addons/#custom-addons), if you are facing any of the below mentioned issues as described in the [cluster autoscaler FAQs](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md): +You can customize the cluster autoscaler addon in order to override the cluster autoscaler deployment definition to set or pass the required flag(s) by following the instructions provided [in the Addons document]({{< relref "../../architecture/concept/kkp-concepts/addons/#custom-addons" >}}). -* [My cluster is below minimum / above maximum number of nodes, but CA did not fix that! Why?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why) +* [My cluster is below minimum / above maximum number of nodes, but CA did not fix that! Why?](https://github.com/kubernetes/autoscaler/blob/aff50d773e42f95baaae300f27e3b2e9cba1ea1b/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why) -* [I'm running cluster with nodes in multiple zones for HA purposes. Is that supported by Cluster Autoscaler?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler) +* [I'm running cluster with nodes in multiple zones for HA purposes. Is that supported by Cluster Autoscaler?](https://github.com/kubernetes/autoscaler/blob/aff50d773e42f95baaae300f27e3b2e9cba1ea1b/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler) ## Summary diff --git a/content/kubermatic/v2.25/tutorials-howtos/kkp-autoscaler/_index.en.md b/content/kubermatic/v2.25/tutorials-howtos/kkp-autoscaler/_index.en.md index 7c18f50c3..2069273ec 100644 --- a/content/kubermatic/v2.25/tutorials-howtos/kkp-autoscaler/_index.en.md +++ b/content/kubermatic/v2.25/tutorials-howtos/kkp-autoscaler/_index.en.md @@ -192,11 +192,11 @@ You can delete autoscaler from where you edit it above and select delete. ## Customize KKP Autoscaler -You can customize the cluster autoscaler addon in order to override the cluster autoscaler deployment definition to set or pass the required flag(s) by following the instructions provided over [here](https://docs.kubermatic.com/kubermatic/v2.25/architecture/concept/kkp-concepts/addons/#custom-addons), if you are facing any of the below mentioned issues as described in the [cluster autoscaler FAQs](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md): +You can customize the cluster autoscaler addon in order to override the cluster autoscaler deployment definition to set or pass the required flag(s) by following the instructions provided [in the Addons document]({{< relref "../../architecture/concept/kkp-concepts/addons/#custom-addons" >}}). -* [My cluster is below minimum / above maximum number of nodes, but CA did not fix that! Why?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why) +* [My cluster is below minimum / above maximum number of nodes, but CA did not fix that! Why?](https://github.com/kubernetes/autoscaler/blob/aff50d773e42f95baaae300f27e3b2e9cba1ea1b/cluster-autoscaler/FAQ.md#my-cluster-is-below-minimum--above-maximum-number-of-nodes-but-ca-did-not-fix-that-why) -* [I'm running cluster with nodes in multiple zones for HA purposes. Is that supported by Cluster Autoscaler?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler) +* [I'm running cluster with nodes in multiple zones for HA purposes. Is that supported by Cluster Autoscaler?](https://github.com/kubernetes/autoscaler/blob/aff50d773e42f95baaae300f27e3b2e9cba1ea1b/cluster-autoscaler/FAQ.md#im-running-cluster-with-nodes-in-multiple-zones-for-ha-purposes-is-that-supported-by-cluster-autoscaler) ## Summary