Open aviramha opened 2 months ago
I've just realized that kubectl doesn't respect SOCKS_PROXY or HTTP_PROXY, only HTTPS_PROXY (but it does respect it when in kubeconfig)
I think we should have same logic
Open PR upstream - https://github.com/kube-rs/kube/pull/1587
Some first time enterprise users fail to use mirrord because of proxy used - sometimes they realize they need to disable use_proxy but on KubeApi if user had no explicitly set proxy settings we can retry with proxy disabled to provide smoother UX