-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Terraform Google provider >= 2.4 throws error: "node_pool": conflicts with remove_default_node_pool #143
Comments
I've also tried specifying If I lock to provider "google" {
version = "~> 2.0.0"
project = "<PROJECT ID>"
region = "us-central1"
zone = "us-central1-a"
}
provider "google-beta" {
version = "~> 2.0.0"
project = "<PROJECT ID>"
region = "us-central1"
zone = "us-central1-a"
}
module "gke" {
providers = {
google ="google-beta"
}
source = "terraform-google-modules/kubernetes-engine/google"
# abbreviated Gives:
|
Can you try locking to |
@morgante I can confirm that locking both |
That's sorted it for me too. Thanks! In general, how should I be determining what provider version is compatible with modules in terraform-google-modules? There's a section in the main README.md but it suggests v2.0.0 is required at present. |
@morgante - that example link seems out of date as it has them pinned to v2.2.x at the moment, which is broken. Are the integration tests running and passing on this module at the moment? Can we look to those to see what provider version should be working? |
@dijitali So our pinning was slightly broken, which is why I have a PR to fix it but 2.2 and 2.3 should probably both work. |
I'm just trying out this module for a PoC and ran into some difficulties following the v2.0.0 release. I created a cluster OK using with v1.0.1 but just upgraded and am now getting this error when running a plan.
I've stripped back my config and still see the same issue with the main example config in the
README.md
I'm not setting
remove_default_node_pool
option but have tried explicitly setting bothtrue
andfalse
and get the same error.Terraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Terraform creates plan successfully.
Actual Behavior
terraform plan
errors withSteps to Reproduce
terraform plan
The text was updated successfully, but these errors were encountered: