-
-
Notifications
You must be signed in to change notification settings - Fork 552
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
Autoscaling does not scale cluster to min capacity on creation #432
Comments
We have encountered the same issue recently, and found that the auto scaling policy is created, but seems to be inactive. By modifying the autoscaling policy, simply editing and saving, the auto scaler kicks in and creates the desired minimum instances. |
this appears to be related to an upstream issue hashicorp/terraform-provider-aws#31329 |
This issue has been automatically marked as stale because it has been open 30 days |
@bryantbiggs I don't think it's directly related to the provider issue, given that it can be fixed by setting explicit dependency on whole module, as I described above. |
This issue has been automatically marked as stale because it has been open 30 days |
This issue was automatically closed because of stale in 10 days |
Description
When creating a cluster with autoscaling enabled, cluster is not automatically scaled to
autoscaling_min_capacity
value and remains stuck with directly created instances.Versions
Module version [Required]: 9.0.0
Terraform version:
1.7.2
Provider version(s):
5.35.0
Reproduction Code [Required]
Steps to reproduce the behavior:
terraform apply
Expected behavior
Reader nodes are scaled to the minimum capacity when cluster becomes available.
Actual behavior
Cluster will be created with only one instance. Autoscaling configuration will not add any reader nodes.
Additional context
If you set
autoscaling_enabled
tofalse
and createaws_appautoscaling_target
andaws_appautoscaling_policy
outside the module withdepends_on
set to whole module reader nodes are created as expected.The text was updated successfully, but these errors were encountered: