Field manager name conflicts for resources created with client-side apply

[lblackstone]

What happened?

Recent versions of kubernetes began setting a field manager for all resources based on the name of the executable performing the update, even for resources managed using client-side apply. This can cause problems for resources that were created using client-side apply that are subsequently updated using server-side apply because the field manager name may conflict.

Related: #2262

Expected Behavior

Updating a resource created using client-side apply mode should not cause conflicts based on the field manager name.

Steps to reproduce

1. Create a resource using client-side apply mode with pulumi-kubernetes
2. Change the provider to use SSA mode and update a value on the resource
3. Run an update
4. The field manager name will conflict and raise an error

Example:

import * as k8s from "@pulumi/kubernetes";

const provider = new k8s.Provider("k8s", {
    enableServerSideApply: false, // change to true on step 2
});
const appLabels = { app: "nginx" };
const deployment = new k8s.apps.v1.Deployment("nginx", {
    spec: {
        selector: {matchLabels: appLabels},
        replicas: 3,
        template: {
            metadata: {labels: appLabels},
            spec: {
                containers: [
                    {
                        name: "nginx",
                        image: "nginx:1.16", // change to "nginx:1.17" on step 2
                    },
                ],
            },
        },
    }
}, {provider});

Results in the following error:

  kubernetes:apps/v1:Deployment (nginx):
    error: Preview failed: 1 error occurred:
    	* the Kubernetes API server reported that "default/nginx-f43bda57" 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
    : Apply failed with 1 conflict: conflict with "pulumi-resource-kubernetes" using apps/v1: .spec.template.spec.containers[name="nginx"].image

Output of pulumi about

n/a

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).