Hey all, I came by a super weird behavior in the pulumi-kubernetes provider Why is the

Kubeconfig

even a part of the state. If it’s the file content - than it may contain secrets. If

Kubeconfig

is a path to a local file - then it may not (and probably won’t) exist later on (CI/CD, different developers). I also saw that

pulumi up

overrides this parameter, so it make even less sense to me. What is interesting thought, and the reason I’m interested in this parameter from the first place is the fact that

pulumi refresh

fails since it is not being overridden in that scenario and tries to find that file locally - with a horrible undescriptive message

warning: configured Kubernetes cluster is unreachable: failed to parse kubeconfig data in `kubernetes:config:kubeconfig`- couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\""; Kind string "json:\"kind,omitempty\"" }
    error: Preview failed: failed to read resource state due to unreachable cluster. If the cluster has been deleted, you can edit the pulumi state to remove this resource