Replies: 3 comments
-
@stubbi You have to check the autoscaler pod logs, see what is happening. |
Beta Was this translation helpful? Give feedback.
-
@stubbi Was your previews try with cilium too? Try without cilium, and as started about, the key is probably in the logs of the autoscaler pod. |
Beta Was this translation helpful? Give feedback.
-
@mysticaltech sorry for my late reply. I do enable the cilium cni. To me it appears that the autoscaler deployment is only there when I configure at least one non-autoscaler node:
I had deployed the cluster 26min ago with only autoscaler node group and min=0, max=5. When I was looking for the autoscaler pod, there was none, nor had the deployment been there. Only after adding a non-autoscaler node it's there now and new nodes are being added on the fly. Realistically, I can set the min workers to 1. I will test if that makes a difference. Though I believe it should work with min workers=0 and no additional fixed nodes and it used to do so. |
Beta Was this translation helpful? Give feedback.
-
Description
Hi there,
It seems I cannot create autoscaler nodepools without creating at least one non-autoscaler node? This was working in an older version.
Kube.tf file
Screenshots
No response
Platform
Mac
Beta Was this translation helpful? Give feedback.
All reactions