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

A) I'm think we just use the standard kubectl config settings so I'd think we'd be using the same config as kubectl
B) You can try turning on debug log (`-v11 --logtostderr`) to see if that prints anything informative

I did that, but couldn’t find out more than what I reported, unfortunately. Can you take a look? Will send redacted logs.

I can you can email logs to me if you want: fraser at <http://pulumi.com|pulumi.com>

I'll admit my k8s knowledge is not the best in the team, but I might spot something and I can ask the experts when they come online later

<@U02J3T6A8LB> I managed to solve/avoid the problem by redoing the setup and skipping kubectl context creation. Please support this PR for others to avoid this issue: <https://github.com/pulumi/registry/pull/1589>

<@U02J3T6A8LB> Additionally, the Pulumi CLI failure mode needs improvement. See <https://github.com/pulumi/pulumi-kubernetes/issues/2202>

Thanks for those. I'll nudge our k8s experts to check the docs update, I think I can fix the second one in our engine without needing to make a k8s specific fix.