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

`PodIdentityProfile` seems to be a property of `ManagedCluster` . Why don’t you define it as part of the cluster definitions, similar to <https://www.pulumi.com/docs/reference/pkg/azure-native/containerservice/managedcluster/#create-managed-cluster-with-podidentity-enabled> ?

&gt; Is there a recommended way to perform updates on existing resources?
We recommend you avoid the need for this, if possible. Aren’t you defining the cluster in your program?

Hi <@UB39JFCKC>. If I define my `PodIdentityProfile` as part of my `ManagedCluster` definition as such:

`PodIdentityProfile = new ManagedClusterPodIdentityProfileArgs`
`{`
  `Enabled = true,`
  `UserAssignedIdentities = new ManagedClusterPodIdentityArgs`
  `{`
     `Identity = new UserAssignedIdentityArgs`
     `{`
       `ClientId = pod_identity.ClientId.Apply(id =&gt; id),`
       `ObjectId = pod_identity.PrincipalId.Apply(id =&gt; id),`
       `ResourceId = pod_identity.Id.Apply(id =&gt; id)`
     `},`
     `Name = "pod-id-tag",`
     `Namespace = "pod-id"`
  `}`
`},`

I get the following error:

`azure-native:containerservice:ManagedCluster (auto-aks):`
    `error: Code="PodIdentityAddonUserAssignedIdentitiesNotAllowedInCreation" Message="PodIdentity addon does not support assigning pod identities on creation."`

This lines up with the AZ CLI which first has me create the aks cluster with the `--enable-pod-identity` flag, and then use `az aks update` to actually set the pod identity info.

I'm trying to figure out how to set my user identity for my pod identity, but can't seem to figure it out.

The problem is that the `PodIdentityProfile` isn't editable after creation (which makes sense).

This doesn’t answer your question but I opened <https://github.com/Azure/azure-rest-api-specs/issues/13417> to track a potential fix upstream

Thanks <@UB39JFCKC>. I'll keep an eye on it. And just for my knowledge, since I'm new to Pulumi, what is the recommended approach if you need to update an existing resource in Pulumi? For example, if I decide to enable the cluster autoscaler after the cluster has been created? Thank you!

You change your program and run `pulumi up` again. Or did I misunderstand the question?

Thanks again <@UB39JFCKC> ... yes, that helps. Really appreciate the help here. Thank you!

Yes, that did solve my problem. I ended up using some configuration to run my Stack, but only performing certain actions if it's a `create` versus an `update`.