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

I think this is because recently I observed that, when rolling out a container environment, azure rolls out some elements of an AKS cluster as well. But pulumi doesn't know this, so it just fails

provider.sh

<@UMYAQ5MC3> I was looking into a ConnectedCluster problem earlier today and I had to register these namespaces as well. I brew this using our Command provider:
```k8s_resource_provider = local.Command(
    "k8s_resource_provider",
    create="./provider.sh register 'Microsoft.Kubernetes'",
    delete="./provider.sh unregister 'Microsoft.Kubernetes'",
)```
With the attached script. Remark that registering/unregistering these providers is for your whole Azure subscription so don't run this in multiple stacks working in the same subscription.

Thanks for the script.. will look into it