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
When creating a worker pool attachment in a new zone, it should wait for the default ALBs (private and public) in the new zones to finish associating to the cluster.
Actual Behavior
The worker pool zone attachment only waits for the new workers to become ready, and finishes before the new ALBs to come up in the new zones. This causes issues in my use case above, to go ahead and disable the ALBs and Terraform apply will fail since the ALB creation is still underway. disable_public_alb1 works as expected because ibm_container_cluster waits for ALBs to finish, but is not the case with ibm_container_worker_pool_zone_attachment.
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
When creating a worker pool attachment in a new zone, it should wait for the default ALBs (private and public) in the new zones to finish associating to the cluster.
Actual Behavior
The worker pool zone attachment only waits for the new workers to become ready, and finishes before the new ALBs to come up in the new zones. This causes issues in my use case above, to go ahead and disable the ALBs and Terraform apply will fail since the ALB creation is still underway.
disable_public_alb1
works as expected becauseibm_container_cluster
waits for ALBs to finish, but is not the case withibm_container_worker_pool_zone_attachment
.Steps to Reproduce
terraform apply
References
The text was updated successfully, but these errors were encountered: