I have an AKS cluster that has been created and is supposed to be managed by Pulumi, however Pulumi is really trigger-happy about replacing the cluster. For example right now the node pools are not in the exact order pulumi expects, which is causing it to want to replace the entire cluster. This is a bit impractical as I'm running stateful workloads on the cluster, where I would be really sad if they lost their state. Making Pulumi completely ignore the node pools is also not an option, as I do need to be able to apply some changes to them going forward, such as changing the min/max counts and such. Is there a way to make this experience better?