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

just upgraded my `@pulumi/gcp` from 0.17.4 to 0.18.3 and now pulumi is determined that it wants to replace my gke cluster with no changes.  anyone got any tips for getting it to behave?

I would guess this might be related to some of the issues noted in <https://github.com/pulumi/pulumi-gcp/issues/88>. There are some notes in <https://github.com/pulumi/pulumi-gcp/issues/88#issuecomment-480848030> on how you can debug this. Feel free to DM me if needed to help diagnose and fix. 

the debugging notes helped, thanks!
ended up having to remove my
```
masterAuth: {
  username: "",
  password: ""
}
``` block