-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GKE cluster cluster_dns_provider doesn't get applied #1833
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Facing the same issue here. Any update on this? |
This is still relevant. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
We run into the same issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR
Only if
cluster_dns_provider
is set to "CLOUD_DNS" it is actually applied. Other valid values would be "PROVIDER_UNSPECIFIED" or "PLATFORM_DEFAULT". Setting the variable to those values doesn't have any effect because of the condition interraform-google-kubernetes-engine/modules/private-cluster/cluster.tf
Line 181 in c81c2fe
This leads to the problem that after a value was set via GCP UI or gcloud CLI, terraform would recreate the cluster:
Terraform Configuration
Expected behavior
All valid values get applied.
Observed behavior
Only if
cluster_dns_provider
is set to "CLOUD_DNS" it is actually appliedTerraform Configuration
Terraform Version
Additional information
#1783
The text was updated successfully, but these errors were encountered: