Is there a way to figure out why pulumi is deleting and replacing some resources instead of updating them? I'm changing the

data

of a configMap and it wants to delete-replace the configMap, and the deployment that refers to it, causing downtime.

--kubernetes:core/v1:ConfigMap: (delete-replaced)
    [id=default/project-internal-tools-service-common]
    [urn=urn:pulumi:internal-tools.dev::project-internal-tools::kubernetes:core/v1:ConfigMap::common]
    [provider=urn:pulumi:internal-tools.dev::project-internal-tools::pulumi:providers:kubernetes::eks::...]
+-kubernetes:core/v1:ConfigMap: (replace)
    [id=default/project-internal-tools-service-common]
    [urn=urn:pulumi:internal-tools.dev::project-internal-tools::kubernetes:core/v1:ConfigMap::common]
    [provider=urn:pulumi:internal-tools.dev::project-internal-tools::pulumi:providers:kubernetes::eks::...]
    ~ data: {
        + FOO: "bar"
    }
++kubernetes:core/v1:ConfigMap: (create-replacement)
    [id=default/project-internal-tools-service-common]
    [urn=urn:pulumi:internal-tools.dev::project-internal-tools::kubernetes:core/v1:ConfigMap::common]
    [provider=urn:pulumi:internal-tools.dev::project-internal-tools::pulumi:providers:kubernetes::eks::...]
    ~ data: {
        + FOO: "bar"
    }

(this configMap was not initially created by Pulumi, it was imported)

is the data different?

Yes

can you open an issue for this? we should be able to support replacing this in place I believe if it supports a patch mechanism

Will do 🙂 Done: https://github.com/pulumi/pulumi-kubernetes/issues/1567