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

Hey James. Its sounding like an engine bug- the change in providers should trigger a replace for the k8s resources. Looks like you opened <https://github.com/pulumi/pulumi-kubernetes/issues/1730> - thanks for doing that! Would you mind adding some code for your cluster? If not I will try to repro it today.

As far as visibility - running a preview like this `pulumi -d --logflow --logtostderr -v=9 pre 2&gt;&amp;1 | tee /tmp/logs`  should dump detailed logs from the engine and the provider in question.

The engine logs for the above would be hugely useful too

I'll see if I can reproduce it for you...