Repository navigation
Replies: 1 comment 8 replies
|
Thanks for the report. The error points to an HTTP proxy connection failure. I checked and I see that sofka’s Kubernetes client reads HTTPS_PROXY but does not respect NO_PROXY. This could explain why kubectl works. The last command removes the HTTPS proxy settings for that run only. If it connects, this confirms that the environment proxy causes the failure. These commands print directly to the terminal, so you can copy the output without the interactive screen. Check names and paths before sharing it. The context picker appears after a connection failure. It lists only default because that is the only context in your kubeconfig. |
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The kubeconfig is set via KUBECONFIG environment variable and contains:
If I start sofka I'll get this error:
BTW: It really sux, that I have to write down the error message manually here, because copy&paste in the terminal (Linux) doesn't work.
A box is giving me the choice to select either "default" and nothing else. kubectl is working fine with that setup. What else is wrong with it?
All reactions