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

Sorry you’re hitting this, I think this warrants a bug report, would you mind filing an issue?

As jaxxstorm said, this sounds like a bug.

As a workaround, can you try adding `ignoreChanges: ["properties.nodeTaints"]` (or the correct resource property name) to see if Pulumi will ignore those and allow the update to proceed?

Adding ignoreChanges: [ "nodeTaints" ] didn't work, but adding "count" (which is what was causing the stack to currently think it needed to update the resource) did prevent Pulumi from trying to update the agent pool and failing.

But if we ever want to change the maxCount/etc. we will hit this again unless we also ignore changes on those properties..

Understood. That's meant as a workaround for now to hopefully "unstick" you.

Could you open an issue at <https://github.com/pulumi/pulumi-azure-native> with the code and steps to reproduce this?

Pulumi update issues with AKS clusters · Issue #959 · pulumi/pulumi-azure-native (<http://github.com|github.com><https://github.com/pulumi/pulumi-azure-native/issues/959|)>

Put both issues in the same bug. You can split them if needed.

Thank you. I will chat with some people internally.