Hi Pulumian, I am stuck with my

pulumi preview

being entirely stuck after changing my GKE cluster from having a public IP for it's Kubernetes Control Plane to a private IP. I am using Twingate and can access the GKE cluster with no problems, but Pulumi seems to want to replace the

provider

for every Kubernetes resource and it seems to be stuck taking an enormous amount of time doing this. What should I try? Any clues?

This sounds like Pulumi believes that you have a new cluster, because you changed the way you connect with it. Last year, a

clusterIdentifier

option was added that prevents this from happening: https://www.pulumi.com/registry/packages/kubernetes/api-docs/provider/#clusteridentifier_go (see https://github.com/pulumi/pulumi-kubernetes/issues/2745 for a description of the problem).

@modern-zebra-45309 Ah. Thank you for sharing 🙏 (I'm glad that I reached out, since I don't think that I would have found this otherwise) A minor note: I feel like this should definitely be emphasized in the documentation. Also, I feel like this is the kind of thing that really does need better DX. The manually editing and applying updates to the

state.json

to fix this is extremely unfriendly IMHO and it is far from the first time that I have had to edit the

state.json

. Ideally some kind of automatic fixing tools for situations like this would be great. e.g.

pulumi adopt clusterIdentifier my-provider-name-urn

which would automatically read your code, find what the new

cluster_identifier

value was and then apply that to the state so that you could then immediately run

pulumi up

cleanly. Does that make sense? Is this something that you are considering internally? Improving the tooling when handling state issues?

Note that I'm just a fellow Pulumi user who has been bitten by similar issues in the past 🙂 I'm very glad that we got the

clusterIdentifier

option last year, and I agree that DX could be improved further. The original Slack thread is no longer available, so I'll ping @hallowed-photographer-31251 and @damp-airline-38442 who led the discussion and implementation.

Thank you @modern-zebra-45309 🙂 My fault for assuming that you were from the Pulumi team