-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https_proxy not working in v0.8.3 #128
Comments
Hi, |
Correct, I tried with all variants of http_proxy https_proxy and in uppercase with no joy. The keywords that I was using to begin with was your own system_smoke.robot tests, and nothing worked. Once I'd made those changes then I was able to get it running just fine. For info, I am also using kubernetes==22.6.0 if that helps any as well. |
Just some more information based on my tests with v0.8.3 prior to making changes.
|
So just wondering how do you mimic proxy on your localhost? Also did some check and seems proxy settings are propagating to all the api clients. Which kubernetes python client version are you using? Also could you double check if no_proxy is not set? |
So, for proxy I'm actually redirecting my http_proxy over socks5 to reach a server that I can only reach via a jumphost.
So I have an SSH session opened to my target server using a ProxyJump and DynamicForward 1080 in my ssh config file etc. Then while keeping that session open, I then have the hpts command running in another terminal, and then I can kubectl to my hearts content... Re: python client, it is. kubernetes==25.3.0 |
Hi, The fix is ready in #129 . Review and possible testing is appreciated. |
I was unable to get a working connection to a kubernetes cluster (v1.21.2) while using the environment variable HTTPS_PROXY, connectivity to the cluster is working for kubectl.
Looking at the code it would appear that it is only checking for http_proxy/HTTP_PROXY, and setting those environment variables also failed to successfully connect to the cluster.
Removing the above code, and adding the following code instead after the config.load_kube_config(...) resolves the issue and proxy works just fine for KubeLibrary.
The text was updated successfully, but these errors were encountered: