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

Using `k8s.rbac.v1.ClusterRole` with Azure AKS, I get this even while recreating a stack from scratch (destroy, then up):
```Diagnostics:
  &lt;kubernetes:rbac.authorization.k8s.io/v1:ClusterRole&gt; (clusterRole-storage):
    error: resource system:azure-cloud-provider was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "system:azure-cloud-provider" already exists```
Is this expected? What should I be doing ideally?

That message is coming from the k8s api server, which means that ClusterRole is already present on the cluster. You would have to import and then update the existing role if you want to manage it with Pulumi.