No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@UG53R9UJC> I would suggest to use a named version - it’s something we have moved to do in Pulumi/examples repo because of these spurious differences :(

I am changing to

```
        minMasterVersion: "latest",
        nodeVersion: "~", // means same as master version
```

and changing "description" to make update "meaningful" from GCP API point of view, lets see how it goes

Ha replace, not good :slightly_smiling_face:

```
    +-gcp:container/cluster:Cluster: (replace)
        [id=gke01-london]
        [urn=urn:pulumi:gke01-london::gcp-gke::gcp:container/cluster:Cluster::gke01-london]
        [provider=urn:pulumi:gke01-london::gcp-gke::pulumi:providers:gcp::default_1_0_0_beta_1::1a4df25a-af6f-4fda-80df-2c8bd047655a]
      + description     : "xxx"
      ~ minMasterVersion: "1.13.7-gke.19" =&gt; "latest"
      ~ nodeVersion     : "1.13.7-gke.19" =&gt; "~"
```

I am actually not sure what ~ will mean for us - because that’s evaluated at the gcp level not Pulumi  level

turned out `~` is not supported by TF provider on cluster creation :slightly_smiling_face: leaving it out completely then, it seems to affect only default nodepool which gets deleted anyway