search

derailed / k9s

🐶 Kubernetes CLI To Manage Your Clusters In Style!
https://k9scli.io
Apache License 2.0
25.92k stars 1.62k forks source link

support https_proxy #371

Open amwais opened 4 years ago

amwais commented 4 years ago

Hi!

Is there a way to connect k9s via https proxy?

The cluster i need k9s to connect to is behind a proxy, therefore I use "https_proxy= kubectl"

I'd really like to use k9s with it.

Many thanks!

alexanderbuth commented 4 years ago

Hi @derailed, is there already a plan when proxy connection is going to be supported? Thanks Alex

mklettner commented 4 years ago

Need this feature too. Would save me lot of time.

mklettner commented 4 years ago

It's working with the correct env var: export HTTPS_PROXY= and if it is an SSL intercepting proxy, you have to use the insecure param: k9s --insecure-skip-tls-verify

jsoref commented 4 years ago

Fwiw, in general, most unix users expect the lowercase format. It's true that these variables don't match the rest of unix, but, that's history. https://unix.stackexchange.com/questions/212894/whats-the-right-format-for-the-http-proxy-environment-variable-caps-or-no-ca

rocketraman commented 4 years ago

I created https://github.com/derailed/k9s/issues/825 for general proxy support. As I explained in that issue https_proxy (or HTTPS_PROXY) isn't a great solution because the proxy used often differs between cluster contexts, and this makes it impossible to switch contexts inside k9s without restarting it with a different environment.

rocketraman commented 4 years ago

~BTW, the uppercase HTTPS_PROXY doesn't work for me either, on 0.21.4.~ Edit: nope, it did finally work after a couple of restarts.

amwais commented 2 years ago

Simply running k9s with https_proxy= should work.

Example: "https_proxy= k9s"

On Wed, 15 Dec 2021 at 19:23, Dieter De Meyer @.***> wrote:

Did someone manage to get this working ? Can someone describe the steps for which it's working ? I've been trying as well using the suggestions above but it's not working...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/derailed/k9s/issues/371#issuecomment-995049942, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG6A63KLXGFWYPCHOJDRRG3URDMINANCNFSM4JCH5SHA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.