Decouple pod_range from enable_private_nodes in node_pools

[M4C4R]

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

node_pools = [
    {
      name         = "central-ciqa"
      machine_type = "e2-medium"
      # per zone
      node_count  = 1
      preemptible = true
      autoscaling = false
      enable_private_nodes = true
    },
  ]

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 with enable_private_nodes and this has been raised before:

• feat: enable_private_nodes on nodepool lvl withour pod_range #1870