Skip to content
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

Proxy Support #1966

Open
lupaulus opened this issue May 9, 2024 · 9 comments
Open

Proxy Support #1966

lupaulus opened this issue May 9, 2024 · 9 comments
Labels
enhancement New feature or request

Comments

@lupaulus
Copy link

lupaulus commented May 9, 2024

Hey very nice project,

It is possible to add proxy settings to use the software inside a corporate proxy network ?

Greetings,

@joaquimrocha
Copy link
Collaborator

@lupaulus You mean the desktop version, right? (Just to be sure)

@lupaulus
Copy link
Author

Yes headlamp desktop

@joaquimrocha joaquimrocha added the enhancement New feature or request label Jun 18, 2024
@joaquimrocha joaquimrocha assigned vyncent-t and unassigned vyncent-t Jun 18, 2024
@yolossn
Copy link
Contributor

yolossn commented Jun 26, 2024

Hey @lupaulus May I know how do you setup proxy for other tools(like kubectl) that interact with the cluster? I was wondering if this can be solved by using the proxy-url config that is supported by kubeconfig .
Refer

@lupaulus
Copy link
Author

With K9s, I setup two entry variable at the startup like in linux : http_proxy=<http_proxy> https_proxy=<https_proxy>

@omniproc
Copy link

omniproc commented Jul 3, 2024

proxy support would require at least http_proxy, https_proxy and no_proxy env vars to be configurable. However please be aware that there is no format syntax definition for the values of those environment variables. Also you might want to add those options to the headlamp settings because you might want different proxy settings for headlamp instead using global environment variables (not a big deal on Linux, but on other platforms it is).

@aoktox
Copy link

aoktox commented Jul 12, 2024

➕ 1️⃣ For this feature, i'm expecting that headlamp aware of proxy-url which supported by kubeconfig

Currently i'm using this workaround, starting headlamp from CLI

$ export HTTPS_PROXY=socks5://localhost:8080
$ /Applications/Headlamp.app/Contents/MacOS/Headlamp

@yolossn
Copy link
Contributor

yolossn commented Jul 16, 2024

@joaquimrocha Should we add an option in the UI to configure the proxy for each cluster? We wont be able to fetch the value from the CLI when running in app mode.

@illume
Copy link
Collaborator

illume commented Jul 16, 2024

There's also OS specific proxy settings. Not sure the current best way to get them, but there's an older article here with a few pointers and explanation: https://evandontje.com/2020/04/02/automatic-system-proxy-configuration-for-electron-applications/

@sysdev41
Copy link

@joaquimrocha Should we add an option in the UI to configure the proxy for each cluster? We wont be able to fetch the value from the CLI when running in app mode.

that would be really great, because I access my clusters via socks5 proxy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

8 participants