priority order between multiple autoscalable worker node pools ? #729
Unanswered
4FunAndProfit
asked this question in
Q&A
Replies: 1 comment 5 replies
-
|
Hi, hetzner-k3s sets up the autoscaler but the functionality available for the autoscaling depends on the specific implementation of the cluster autoscaler for the provider, in this case Hetzner. I am not aware of any feature in such implementation that would allow you to define a priority order between multiple autoscalable worker node pools. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello @vitobotta
(Yes I have another question sorry haha)
Does hetzner-k3s support defining a priority order between multiple autoscalable worker node pools (for example: scale a cheaper instance pool first, and only fall back to more expensive pools if needed because availability )?
More specifically: does the order of worker_node_pools in the YAML configuration matter, or is the only way to influence this behavior through pod scheduling constraints such as nodeAffinity, nodeSelector, or similar mechanisms?
Thanks a lot in advance ! :)
PS : saw this I don't know if it is compatible https://docs.digitalocean.com/products/kubernetes/how-to/autoscale/?utm_source=chatgpt.com#configuring-priority-expander with a configmap
Beta Was this translation helpful? Give feedback.
All reactions