No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Update: Seems like Pulumi stores where `kubeconfig` is, which is probably caused by the fact that we configure default `namespace` . The `kubeconfig` variable is set to the wrong path in the state file.

Hypothesis: This causes Pulumi look in the wrong path for credentials, even though correct credentials are passed. The credentials are never updated, because it fails on something else.

<@UMP2PT80L> are you using explicit providers on your k8s resources?

After changing path in the `kubeconfig` manually to `~/.kube/config` in the state file, I'm able to apply stuff.

if you're using explicit providers, it will indeed embed the kubeconfig into your state

I also think that Google's new Github Actions uses a temporary path for `kubeconfig`

Okay, so to strengthen this setup, we should probably use explicit namespaces and remove providers? What do you think?

Maybe ensure the `kubeconfig` is always in the same path, since we're always up-ing from Github Actions anyway.

i usually build my kubeconfig from a stack reference, so it's always the same, but if you're reading from a file, ensuring it's always in the right place will definitely help

Hm, maybe there's something we can with the Kubernetes provider for this?