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

Hey guys.  Have a quick question in regards to how Pulumi derives the managed field manager name for Kubernetes.  In my case, I'm doing some testing with the new `k8s.helm.v4.Chart` resource.  I'm currently using it to deploy the Cilium CNI.  I deploy a new cluster.  So, nothing really there other than the control plane.  Then run Pulumi.  Cilium deploys as expected.  No trouble there.  If I edit a piece of the configuration and try to run Pulumi again, I get apply conflict errors.

```The resource managed by field manager "pulumi-kubernetes-80a7e523" had an apply conflict: Apply failed with 2 conflicts: conflicts with "pulumi-kubernetes-375c67bb":```
Normally, I would suspect something like the operator touching the field and then Pulumi throwing the error because that managed field changed.  However, if you check the error above (and the managed fields configuration on the resource itself), you can see it's still set to `pulumi-kubernetes-xxxxxxxx`.  Am I missing something or is Pulumi somehow conflicting with itself?  Obviously the suffix of the field manager changed.  I just don't know why.