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

To clarify that: the diff for the provider is actually showing something: It's showing that the previous value of the `kubeconfig`is now possibly changing i.e. it says it will be replaced with `output&lt;string&gt;`

i get this quite often with the azure AKS changes

i've manually patched my state file a few times in the last few months it works ok

with AKS it was a matter of changing agentProfile: {} to agentProfiles: [{}]

kubeConfig and stuff becoming output&lt;string&gt; is usually a side effect of the thing causing the change not the actual cause IME

output&lt;string&gt; in the diff means it doesnt know what the value will be until it starts

another cause i had was that the service principal metadata that owns a cluster changed

Thanks, <@UEU2M37GX>. I don't know though what to patch in the state file regarding the EKS cluster because every output the `kubeconfig` property depends on is unchanged seemingly. I tried to set different values and in the exported stack and re-importing it, but the behaviour stays the same :disappointed:

<@UHSPR78E5> I had a (possibly) similar error yesterday with pulumi attempting to replace a resource that has not really changed and the diff being not very useful.
With the help of <@UB3BGTV63> I was able to see what has changed by installing `curl -L <https://get.pulumi.com/> | bash -s -- --version 0.17.23` . This is a very new pulumi version that shows more complete diffs.

Thanks for the advice <@UCPSHLVC4>. I just tried it with `0.17.23` and the output is different for some unrelated CloudFront resources. However, the preview details look the same regarding the Kubernetes provider.