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 specifying enable_l4_ilb_subsetting = false in cluster creation, the cluster gets created with the feature enabled anyway. Because of this, subsequent runs cause a full cluster replacement also with enable_l4_ilb_subsetting enabled.
Expected behavior
Cluster should be created with enable_l4_ilb_subsetting = false
Observed behavior
Cluster is created enable_l4_ilb_subsetting = true causing a replacement cycle every time a change is applied.
Similar issue when I try to change the setting in an existing public cluster (works via google UI):
- Using previously-installed hashicorp/google-beta v4.71.0
- Using previously-installed hashicorp/random v3.5.1
- Using previously-installed hashicorp/google v4.71.0
- Using previously-installed hashicorp/null v3.1.1
- Using previously-installed hashicorp/kubernetes v2.21.1
adding enable_l4_ilb_subsetting = true to an existing cluster results in:
╷
│ Error: Unsupported argument
│
│ on main.tf line 564, in module "gke":
│ 564: enable_l4_ilb_subsetting = true
│
│ An argument named "enable_l4_ilb_subsetting" is not expected here.
╵
TL;DR
When specifying
enable_l4_ilb_subsetting = false
in cluster creation, the cluster gets created with the feature enabled anyway. Because of this, subsequent runs cause a full cluster replacement also with enable_l4_ilb_subsetting enabled.Expected behavior
Cluster should be created with enable_l4_ilb_subsetting = false
Observed behavior
Cluster is created enable_l4_ilb_subsetting = true causing a replacement cycle every time a change is applied.
Terraform Configuration
Terraform Version
Additional information
No response
The text was updated successfully, but these errors were encountered: