You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason is that after cluster creation, almost everyone will run the k8s node autoscaler. This autoscaler is changing the desired_capacity to suit resources required by the cluster. So when the cluster autoscales, then TF is run again later, you see something like this:
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
I'm submitting a
The reason is that after cluster creation, almost everyone will run the k8s node autoscaler. This autoscaler is changing the
desired_capacity
to suit resources required by the cluster. So when the cluster autoscales, then TF is run again later, you see something like this:You can just add a lifecycle statement to resource
aws_autoscaling_group.workers
:The text was updated successfully, but these errors were encountered: