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

Can you share the output of `pulumi preview --diff` so that we can get a better sense of why Pulumi thinks it needs to replace resources?

I seen this exact behavior with Bicep on the Azure virtual desktop (AVD) APIs. Someone smarter than me can review the Azure resource manager (ARM) APIs and see if order matters. 

In my example, I was associating multiple application groups with a workspace. Easy to change the order around if it was not in a for loop. Sometimes the order would be correct on all the workspaces and other times N number would be out of order. I haven’t seen any actual change besides the confirm with what if (Bicep diff) showing a change. I also wasn’t working on an AKS cluster. Do you have a test cluster?

I suggest managing your node pools with the AgentPool api, rather than the inline nodepool property