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

Screenshot 2020-11-13 at 23.41.53.png

We just changed the deletion behavior in <https://github.com/pulumi/pulumi-kubernetes/pull/1379> yesterday, so that should fix issue 2 for you. I’ll cut another release with that fix next week, or you can try it out with a dev build.

For issue 1, that looks more like the wrong data is being passed in for the kubeconfig. It should fail with an auth error if an expired token is the problem.

Awesome, thanks. Okay, regarding 1 sounds weird. While getting this error I’m having k9s running in another tab, using the same credentials from ~/.kube/config which is talking to the cluster fine.

Does pulumi somehow extract the the config and saves it temporarily somewhere? Maybe it gets corrupted in this process?

To me it seems like this kubeconfig that is getting "corrupted" is somehow stored in the stack state? Because if it happens on one device, the same starts happening on other devices trying to provision resources for that stack as well.