-
Notifications
You must be signed in to change notification settings - Fork 61
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
Support proxy-url from ~/.kube/config
#2468
Comments
@flybyray thank you for reporting this. I tested kubectl, oc and odo in exactly the same environment. oc and odo does not support proxy-url in ~/.kube/config as you mentioned above, but they do support https_proxy env variable. Workaround: set https_proxy env manually and then restart vscode. Fix: set https_proxy env var when running oc or odo if current context has proxy-url property set. |
@dgolovin thx i know such workarround but it is not applicable for all use cases, because in this case even vscode + extensions use it and hence things do not work as expected anymore. |
@flybyray thank you for pointing that out. I'm setting higher priority for this issue. |
Fixed by #2502 |
@mohitsuman no it it was related to the issue, but not an actual fix. |
@flybyray @mohitsuman It cannot be fixed for several reasons. I did my best to workaround what I could, but it didn't work.
Basically nether official javascript client nor openshift oc/odo cli are supporting this use case. |
Hence i understand that this extension will not support it if it is not base on |
@flybyray let me check latest |
@flybyray probably I can workaround oc login issue, by getting proxy-url before 'oc login' then adding it back. But any 'oc login' calls outside of vscode will remove proxy-url anyway. |
Related issue in @kubernetes/nodejs-client package kubernetes-client/javascript#853. |
Environment
VS Code version: 1.68.1
OS: win32
Extension version: 0.4.0
Description
I have setup
proxy-url
in~/.kube/config
.Usage description: https://kubernetes.io/docs/tasks/extend-kubernetes/socks5-proxy-access-api/#client-configuration
This works as it should with
oc
from command line.But the extension is not using this property.
The text was updated successfully, but these errors were encountered: