Hi Pulumi peeps! I'm wondering if anyone here has had experience migrating from pure Helm to Pulumi? I did it a few months ago for one of the namespaces in my k8s cluster and it has gone relatively smoothly, but as I make more and more changes to things like container commands or service definitions, I'm increasingly running into field manager conflicts. Basically I try to edit something with pulumi but it refuses the changes server-side because the resource was previously manged by helm (and I guess still is). This is what the errors generally look like upon `pulumi preview`:

kubernetes:core/v1:Service (gateway):
    error: Preview failed: 1 error occurred:
    	* the Kubernetes API server reported that "chains-ethereum/gateway" failed to fully initialize or become live: Server-Side Apply field conflict detected. See <https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources> for troubleshooting help.
    The resource managed by field manager "pulumi-kubernetes-d13aaf31" had an apply conflict: Apply failed with 1 conflict: conflict with "helm" using v1: .spec.type

In my experience, it's key to understand why this error message occurs (Kubernetes docs) and then choose the appropriate solution from the docs linked in the error message. If you haven't scrolled down far enough yet 😉 there's a section for Helm with an example: https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#helm-charts

I was just about to message, I saw you reply this link to someone else upon searching in this channel! Thanks 🙂 I checked it out and it quickly unblocked me

Glad you have a path forward 🙂