Closed ivankatliarchuk closed 2 months ago
This issue has been resolved in version 20.20.0 :tada:
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.
Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.
5.12.0
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group#ignore_failed_scaling_activities
Is your request related to a problem? Please describe.
We have multiple clusters. Size of each ASG is ~200 Nodes. Our workflow is as follow
We manage our infrastructure with Terraform and have multiple clusters, each containing number of Auto Scaling Group (ASG) with roughly 200 nodes each. Our workflow involves a two-step process: plan followed by apply. However, when we attempt to upgrade a cluster and modify the ASGs within this workflow, we frequently encounter an issue where the desired size of the ASG changes outside of Terraform's control. This leads to unexpected behavior and potential bugs.
We follow blue/green upgrade model, when we migrate pods from blue to green ASG. This require to have blue and green asgs.
This soluiotn is not sufficient
This is a commont error code
Describe the solution you'd like.
Add support for
ignore_failed_scaling_activities
it was added to aws provider a year+ ago.Describe alternatives you've considered.
Change to our processes
Additional context