Hey, we're using gke and trying to ugrade the

k8s.Provider

to the new

gke-gcloud-auth-plugin

user:
    exec:
        apiVersion: client.authentication.k8s.io/v1beta1
        command: gke-gcloud-auth-plugin
        installHint: Install gke-gcloud-auth-plugin for use with kubectl by following
          <https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke>
        provideClusterInfo: true

After the change to the provider, pulumi wants to replace all of the kubernetes objects:

+-  ├─ kubernetes:core/v1:Namespace                         namespace1                                                            replace     [diff: ~metadata,provider]
 +-  ├─ kubernetes:core/v1:Namespace                         namespace2                                                            replace     [diff: ~metadata,provider]

i tried adding

ignoreChanges: ['metadata', 'provider']

but it didn't work - it still trying to replace all of the objects. any idea on how to prevent the replacement of all of the objects?

did you try locally first installing the

gke-gcloud-auth-plugin

and fetching new k8s config? Not sure about the recreate (did it 1year ago don;t remember). but what does the details say for the metadata and provider? you are initalizing the provider with

const k8sProvider = new k8s.Provider(`k8s-provider-name`, {
  kubeconfig,
});

also does the

kubeconfig

variable updates correctly?

yes the plugin is already updated locally. the details are just replacing fields in the metadata like manager

~ manager   : "pulumi-resource-kubernetes.exe" => "pulumi-kubernetes-c75463ba"

and some of the managed fields, time etc... and changing the provider (as expected).