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 outcome of the ibm_container_cluster resource is that the cluster will contain a private ALB, but that ALB will be disabled. This is because of the no_subnet = "true" flag.
The ibm_container_worker_pool_zone_attachment edge_pool_zone resource should therefore not wait for the ALB to be enabled. It will never be enabled. (i enable the ALBs later after the edge nodes are active)
Actual Behavior
ibm_container_worker_pool_zone_attachment edge_pool_zone waited for the ALB to be ready. It never became ready due to no_subnet = "true" and the terraform script eventually timed out.
Steps to Reproduce
terraform apply
Important Factoids
None
References
This problem was introduced in v1.5.0 of the plugin via this ticket
Terraform Version
Terraform v0.12.25
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
The outcome of the ibm_container_cluster resource is that the cluster will contain a private ALB, but that ALB will be disabled. This is because of the
no_subnet = "true"
flag.The
ibm_container_worker_pool_zone_attachment edge_pool_zone
resource should therefore not wait for the ALB to be enabled. It will never be enabled. (i enable the ALBs later after the edge nodes are active)Actual Behavior
ibm_container_worker_pool_zone_attachment edge_pool_zone
waited for the ALB to be ready. It never became ready due tono_subnet = "true"
and the terraform script eventually timed out.Steps to Reproduce
terraform apply
Important Factoids
None
References
This problem was introduced in v1.5.0 of the plugin via this ticket
The text was updated successfully, but these errors were encountered: