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

Hi, we are managing AKS clusters using Pulumi with Golang. We typically perform AKS upgrades every quarter. Previously, we are using the package `<http://github.com/pulumi/pulumi-azure-native-sdk/containerservice/v2/v20240501|github.com/pulumi/pulumi-azure-native-sdk/containerservice/v2/v20240501>`, and during upgrades, the cluster upgrade would run in parallel. However, after moving to version 3 (`<http://github.com/pulumi/pulumi-azure-native-sdk/containerservice/v3|github.com/pulumi/pulumi-azure-native-sdk/containerservice/v3>`), We have noticed a behavior change; the upgrades are now running sequentially.

We have not made any changes to our code or how we handle the cluster loop, nor have we altered the `dependsOn` settings. We are unsure if this behavior change is related to the upgrade to v3 of `containerservice`. Could anyone provide insight into this issue? As a workaround, we are using Azure Kubernetes Fleet Manager so that we can still run the upgrade in parallel.

If there's no dependencies between the resources they should be registered at the same time and the provider should process them in parallel