Hello there, I am trying to render yaml without a cluster present. So far, I am unable to do that as the Kubernetes Provider always tries to connect to the cluster described by my current context. Removing the

.kube/config

file doesn't seem to help either. I've also tried setting

KUBECONFIG

to empty string to no avail. Any pointers are appreciated 🙂

I would just run a "noop" cluster locally using kind: https://kind.sigs.k8s.io

That's a good option, however I was hoping to not run anything additional since I am running this in CI, which adds to the build time. I will try to use Kind in CI and measure the resulting build times. Thanks for the response! 🙂

How about

skipUpdateUnreachable

? https://www.pulumi.com/registry/packages/kubernetes/api-docs/provider/#skipupdateunreachable_nodejs

nope 😐 but that's fine, kind adds a minute to our build process which is not a huge deal and will do for now, I'll keep an eye out for any updates to the provider that would allow such a thing. It's better than being connected to an actual cluster. Thank you 🙂

I know we had this issue and resolved it - I've just had a dig through the code to try to work out what we did, we're using the automation API in Golang, using Kubernetes provider 4.18.3, and it's working here when we set

KUBECONFIG

to a nonsense string (we use the word 'unset', fwiw). I'm not sure if it's working here because our setup is different to yours (looks like you're using pulumi CLI with nodejs), but I thought I'd send this on the off chance it's as simple as giving

KUBECONFIG

a nonsense value, rather than an empty string.

I'll give that a try, that would be wonderful! TMI we're using Pulumi in Kotlin! via the Java library

This appears to be a known issue, but I do not know why those two values would be mutually exclusive: https://github.com/pulumi/pulumi-kubernetes/issues/3498