-
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
Decouple pod_range
from enable_private_nodes
in node_pools
#2021
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 |
This is still valid. |
We are also affected by this issue. As mentioned in the documentation, this should work! https://registry.terraform.io/modules/terraform-google-modules/kubernetes-engine/google/latest#node_pools-variable |
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 |
this is still missing? |
TL;DR
We wanted to convert an existing node pool from public to private, so made the following change in our config:
module "kubernetes_engine" { source = "terraform-google-modules/kubernetes-engine/google" version = "31.1.0" ... node_pools = [ { name = "example" machine_type = "e2-medium" # per zone node_count = 1 preemptible = true autoscaling = false + enable_private_nodes = true }, ] ... }
However, no changes were noticed as a part of this.
Expected behavior
I expected my node pool to be converted to private.
Observed behavior
Terraform noticed no changes.
Terraform Configuration
Terraform Version
Terraform v1.7.4 on darwin_arm64 + provider registry.terraform.io/hashicorp/google v5.36.0 + provider registry.terraform.io/hashicorp/kubernetes v2.27.0 + provider registry.terraform.io/hashicorp/random v3.6.2 Your version of Terraform is out of date! The latest version is 1.9.3. You can update by downloading from https://www.terraform.io/downloads.html
Additional information
Seems that
pod_range
is coupled withenable_private_nodes
and this has been raised before:The text was updated successfully, but these errors were encountered: