dynamically create node pools on hetzner? #696
leblancmeneses
started this conversation in
General
Replies: 1 comment 3 replies
-
|
Wow! What would you do with 23 node pools? :D What's the point to have more node pools than even the available instance types? And anyway yes, there is a limit to the size of the whole autoscaler config, because it has to include al the code required to initialize the autoscaled node and set up k3s. Can you elaborate on what you are proposing re: configmap? |
Beta Was this translation helpful? Give feedback.
3 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.
-
[Cluster Autoscaler] : The Deployment "cluster-autoscaler" is invalid: metadata.annotations: Too long: must have at most 262144 bytes"]
This occurs when I try adding 23 total pools upfront.
It seems the config gets serialized and then k8s decides what to create/delete .
I wanted a generic system of pools. If I can't pre-create them is there a way I can dynamically create the pools? I'm trying to build a custom cost optimizer based on hetzner current pricing for my region.
I can create 12 pools (masters spin up but workers with instance: 1 do not):
At 4 pools things work like expected.
If needed, can it be added as a configmap and mounted on cluster-autoscaler?
Beta Was this translation helpful? Give feedback.
All reactions