-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
min_size & desired_size #2030
Comments
hi @dmitry-mightydevops - this is not a bug and is the desired effect. Autoscaling of nodes via cluster autoscaler or Karpenter is the preferred method by many, and unfortunately Terraform does not allow for parameterizing |
Sounds good - thanks @bryantbiggs that's what I thought. |
I'm getting this too (on a cluster I scaled down manually via the console). @bryantbiggs I think this should be reopened. Perhaps the More infoMy terraform plan shows the changes made outside of what the state knows (I had scaled it to 1):
I then see that terraform will increase the min_size:
Then during apply, it fails with:
|
Regarding the comment: #2030 (comment) I suspect it will be possible to handle this properly after this is done: hashicorp/terraform#27360, hashicorp/terraform#3116 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
the group is created. I change the desired_size 1 -> 2, run apply and nothing. It doesn't detect the change because of the following code for the node group
I then try to do
and apply fails with the following error:
So the only way to overcome it is
Is this considered a bug?
Versions
Module version [Required]:
Terraform version: 1.1.8
Provider version(s): 18.20.2
The text was updated successfully, but these errors were encountered: