https://pulumi.com logo
#getting-started
Title
# getting-started
e

early-cat-34152

10/10/2022, 8:27 AM
My Pulumi deployment to a custom cluster in Minikube keeps hanging on "Please enter Username". This seems to come from
kubectl
. But
kubectl
on the CL works fine. How can I find out which user Pulumi is using for authentication?
No one?
e

echoing-dinner-19531

10/13/2022, 9:02 AM
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
e

early-cat-34152

10/13/2022, 9:24 AM
I did that, but couldn’t find out more than what I reported, unfortunately. Can you take a look? Will send redacted logs.
e

echoing-dinner-19531

10/13/2022, 9:34 AM
I can you can email logs to me if you want: fraser at 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
e

early-cat-34152

10/14/2022, 8:06 AM
@echoing-dinner-19531 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
@echoing-dinner-19531 Additionally, the Pulumi CLI failure mode needs improvement. See https://github.com/pulumi/pulumi-kubernetes/issues/2202
e

echoing-dinner-19531

10/14/2022, 8:28 AM
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.
3 Views