OVHcloud Managed Kubernetes service provides you Kubernetes clusters without the hassle of installing or operating them.
During the day-to-day life of your cluster, you may want to dynamically adjust the size of your cluster to accommodate to your workloads. The cluster autoscaler simplifies the task by scaling up or down your OVHcloud Managed Kubernetes cluster to meet the demand of your workloads.
This guide follows up the Using the cluster autoscaler guide, and it will cover a description of the by default cluster autoscaler configuration, and in a near future, how to tweak it.
The cluster auto-scaler feature is currently a beta. We expect it to reach General Availability by Summer 2021.
During this beta phase, the configuration options for the cluster autoscaler are immutable, set to sensible by-default values. We plan to progressively allow our users to modify some of these parameters to better tailor them to their specific use cases.
- An OVHcloud Managed Kubernetes cluster
- A basic understanding of how the cluster autoscaler works and how to enable it.
Cluster autoscaler configuration
When the autoscaler is enabled on a node pool, is uses a default configuration.
Here you have a description of the parameters used in the autoscaler configuration, and their default value:
You can get more information on those parameters on the Kubernetes autoscaler documentation. If you consider we should reevaluate the default value and/or prioritize the possible customization of of one of those parameters, we are looking for your feedback concerning this beta feature in the Gitter community channel around OVHcloud Managed Kubernetes service.
To have an overview of OVHcloud Managed Kubernetes service, you can go to the OVHcloud Managed Kubernetes page.
Otherwise to skip it and learn more about using your Kubernetes cluster the practical way, we invite you to look at our tutorials.