-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Cluster autoscaler requires all migs to be autoscaled #1283
Comments
@mwielgus Please, please, please! Be more verbose in PRs & issues! It'd be very hard for anyone to understand why is it an important bug and what was actually broken. We're working in a large project, with huge community and we should make sure that our people can understand what and why we are doing. This is really important. |
More details were added in the fixing PR approximately 40 min before your comment. #1282 (comment). The issues is quite straightforward and the problem is defined in the title, however I can rephrase it. If one mig in the cluster has autoscaling turned off then CA doesn't work. The exact explanation would be rather impossible without a reference to the implementation so it will be bette handled in the PR. Please take a look at the comment linked above. |
Fixed in #1282. |
Automatic merge from submit-queue Check if Cluster Autoscaler still works if there is an extra non-autoscaled node pool in the cluster Follow up for issue kubernetes-retired/contrib#1283.
Otherwise it doesn't do any scale up or scale down.
The text was updated successfully, but these errors were encountered: