This message was deleted.

After downgrading this project back to the version 17.1 of the

pulumi/gcp

package, i literally had the same issue. Another cluster that is running this same version

pulumi/gcp

version is working properly. Both clusters are using the same Pulumi version (17.2).

cc @white-balloon-205 @stocky-spoon-28903

I think this is likely related to the issues that we’ve seen in CI and elsewhere but have been unable to reproduce. @white-balloon-205, do you think we should roll back the changes in

pulumi-terraform

here?

I can confirm that it’s related to the Kubernetes version. I created another cluster using the version

1.11.7-gke.12

instead of

1.12.5-gke.5

and i had no issues after more than 10 deployments.

What it looks like is that Pulumi is having issues to get the information about the cluster, so it assumes that the cluster has a specific configuration, ignoring that fact it’s protected and triggering unnecessary changes.

Is that possible? I believe the main issue here is how Pulumi behaved in that situation. Assuming a specific resource configuration can lead to a lot of unexpected results and it makes much more difficult to understand what’s really happening.

Opened https://github.com/pulumi/pulumi-gcp/issues/116 to track this so we can get to the bottom of it. It has some similar symptoms to a couple other issues we've seen recently so I'm expecting it is related as @stocky-spoon-28903 notes above.

I’m going to follow from there. Thanks!