-
-
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
EKS ASG Worker Desired Capacity Change being ignored #162
Comments
This is because So currently you would need to set this manually outside of Terraform. Feel free to make a PR to make this setting optional 🙂 |
Thank you for the quick and helpful response. I think the auto-scaler aspect is a fair point. I am fine if this is working as intended for the time being and will make use of the autoscaler once the environment has been bootstrapped. |
OK cool, thanks for the update. |
Would it make sense to exclude |
Sure |
|
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. |
I have issues
For an existing Cluster that has been deployed using version 1.6 I would like to modify the worker counts.
I'm submitting a...
What is the current behavior?
When editing asg_desired_capacity it does not affect terraform plan and the ASG is not modified.
If this is a bug, how to reproduce? Please include a code sample if relevvant.
What's the expected behavior?
Are you able to fix this problem and submit a PR? Link here if you have already.
sry, no.
Environment details
AWS region us-east-1
Any other relevant info
Also testes with 1.7 release. No impact.
.terraform was also removed and terraform init performed.
The text was updated successfully, but these errors were encountered: