GCP GKE Cluster Cloud state and Pulumi state always out of sync

[benglewis]

Describe what happened

I created a GCP GKE cluster with dns_config and it re-creates the dnsConfig on every pulumi up despite no changes to the code or externally to the cluster. pulumi refresh does not help, but can break things when using ignore_changes, which then results in pulumi up failing.

Sample program

gke_cluster = gcp.container.Cluster(
        "gke-cluster",
         ...
        dns_config=gcp.container.ClusterDnsConfigArgs(
            cluster_dns="CLOUD_DNS",
            cluster_dns_domain=k8s_sub_domain,
        ),
        ...
    )

Where k8s_sub_domain is the sub-domain that I use in Google Cloud DNS.

Log output

Here's the diff:

~ gcp:container/cluster:Cluster: (update)
    [id=projects/redacted/locations/redacted/clusters/redacted]
    [urn=urn:pulumi:dev::redacted::gcp:container/cluster:Cluster::redacted]
    [provider=urn:pulumi:dev::redacted::pulumi:providers:gcp::default_8_10_2::50e1eb43-1734-4a29-be83-09b36917f37c]
  ~ dnsConfig: {
      + clusterDnsScope: "DNS_SCOPE_UNSPECIFIED"
    }

Affected Resource(s)

GKE Cluster (i.e. gcp:container/cluster:Cluster)

Output of pulumi about

CLI
Version 3.153.1
Go Version go1.23.6
Go Compiler gc

Plugins
KIND NAME VERSION
resource gcp 8.10.2
resource kubernetes 4.18.4
language python 3.153.1

Host
OS darwin
Version 15.3.1
Arch arm64

This project is written in python: executable='.pixi/envs/dev/bin/python3' version='3.13.1'

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[benglewis]

Looks like this was fixed in the Terraform upstream but not yet released:
hashicorp/terraform-provider-google#21637

[VenelinMartinov]

Hi @benglewis, sorry you hit this and thanks for digging up the upstream fix!

We'll inherit this from the upstream provider soon after they release it, thank you for flagging that up!

[VenelinMartinov]

@benglewis is this fixed in the latest release now? Looks like the TF provider has had a release since the fix and we have pulled that in https://github.com/pulumi/pulumi-gcp/releases/tag/v8.21.0

[benglewis]

This didn't yet fix the issue. I believe that the upstream release did not yet include the fix
Update: It looks like the upstream v6.25.0 includes the fix