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

image.png

i have seen this behavior in a couple environments now and have had to resort to manually deleting the new aks cluster, exporting the stack, deleting all of the k8s resources and the old provider, and regenerating everything again. obviously not ideal. <@UHTP242EB>

attempting to run `up` again after the failed update just results in the same error

Can you open an issue at <https://github.com/pulumi/pulumi-azure> with the Pulumi CLI and package versions you're using and the steps you've performed that got to this state?