TPGv5.44 and Autopilot Clusters

[apeabody]

TL;DR

With TPGv5.44

Error: googleapi: Error 400: Setting node_pool_defaults.node_config_defaults.node_kubelet_config is not allowed on GKE Autopilot clusters

Expected behavior

No response

Observed behavior

No response

Terraform Configuration

TestSimpleAutopilotPrivate 2024-09-09T21:32:28Z command.go:185:       + node_pool_defaults {
TestSimpleAutopilotPrivate 2024-09-09T21:32:28Z command.go:185:           + node_config_defaults {
TestSimpleAutopilotPrivate 2024-09-09T21:32:28Z command.go:185:               + insecure_kubelet_readonly_port_enabled = (known after apply)
TestSimpleAutopilotPrivate 2024-09-09T21:32:28Z command.go:185:               + logging_variant                        = (known after apply)
TestSimpleAutopilotPrivate 2024-09-09T21:32:28Z command.go:185:             }
TestSimpleAutopilotPrivate 2024-09-09T21:32:28Z command.go:185:         }

### Terraform Version

```sh
INT Tests

Additional information

No response

[danihodovic]

I'm still facing this in 35.0.1

terraform {
  cloud {
    organization = "proj"

    workspaces {
      name = "cloud"
    }
  }

  required_providers {
    google = {
      source  = "hashicorp/google"
      version = ">= 6.14.0, < 7"
    }

    google-beta = {
      source  = "hashicorp/google-beta"
      version = ">= 6.14.0, < 7"
    }

    sops = {
      source  = "carlpett/sops"
      version = "~> 0.5"
    }

    helm = {
      source  = "hashicorp/helm"
      version = "2.14.0"
    }
  }
}

module "gke" {
  source                = "terraform-google-modules/kubernetes-engine/google//modules/beta-autopilot-public-cluster"
  version               = "35.0.1"
  project_id            = var.project_id
  name                  = var.cluster_name
  region                = var.region
  network               = local.vpc_name
  subnetwork            = local.subnet_name
  ip_range_services     = local.services_network_name
  ip_range_pods         = local.pods_network_name
  grant_registry_access = true
}

[apeabody]

I'm still facing this in 35.0.1

Hi Dan - Yes, there is a similar issue with Terraform Google Provider 3.17+ which is resolved in #2256 and will be included in the upcoming v36. Alternatively, with v35.0.1 you can try temporarily adding a < 6.17 version constraint for your Terraform Google Providers.