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

``` +-  │  ├─ gcp:container:Cluster                      primary                 replace     [diff: +nodeConfig]
```

cc <@UB8A66MPS> I think there is a known problem where nodepools trigger replacements in the underlying provider, right?

Hmm I do seem to remember that, it’s been a while though

Can you look at the detailed diff <@UPP2LRB61>?

```
Previewing update (prod):                                                                                          pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:prod::et-infra::pulumi:pulumi:Stack::et-infra-prod]                                                  +-gcp:container/cluster:Cluster: (replace)
            [id=primary-7eb95f6]
            [urn=urn:pulumi:prod::et-infra::examples:kubernetes-ts-multicloud:GkeCluster$gcp:container/cluster:Cluster::primary]
            [provider=urn:pulumi:prod::et-infra::pulumi:providers:gcp::default_1_3_0::8b0d3e57-37ca-4df3-9fce-1c4067b96d0b]
          + nodeConfig: {
              + machineType: "n1-standard-1"
              + oauthScopes: [
              +     [0]: "<https://www.googleapis.com/auth/logging.write>"
              +     [1]: "<https://www.googleapis.com/auth/monitoring>"
                ]
              + preemptible: false
            }                                                                                                                +-pulumi:providers:kubernetes: (replace)
            [id=abcfb911-beda-4300-acf0-ad7aa0d9feac]
            [urn=urn:pulumi:prod::et-infra::examples:kubernetes-ts-multicloud:GkeCluster$pulumi:providers:kubernetes::gke]
......```

I removed the `nodeConfig` and it reported no changes

I don't know how far the default nodeConfig for GCP clusters is from that, but if they're going to be torn down immediately it doesn't matter I guess :shrug:

Isn’t there some option like `removeDefaultNodePool`?

(Flying somewhat blink here since its 11.40pm and have no laptop)