You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kube-client crate currently supports only SOCKS5 proxies in the kubeconfig (config.proxy_url, HTTP[S]_PROXY/http[s]_proxy env variables). Relevant code starts here. However, proxy can also use the regular HTTP protocol.
Describe the solution you'd like
Inspect scheme of the proxy URI and optionally wrap the base connector with hyper_proxy. Hide it behind a new feature http_proxy (name suggestions welcome).
I like the proposal of this in theory because I would also like to support it, but it has one problem practically; the proposed crate has not had a release in over 2 years.
If we were to do this, I would personally prefer to do it after the hyper 1.0 upgrade in #1351 (since we are already having to deal with infrequently updated connector libraries there and this feature would compound that). Waiting for 1.0 would mean getting a 1.0 upgrade pushed up into hyper-proxy first though.
Would you like to work on this feature?
yes
What problem are you trying to solve?
kube-client
crate currently supports only SOCKS5 proxies in the kubeconfig (config.proxy_url
,HTTP[S]_PROXY
/http[s]_proxy
env variables). Relevant code starts here. However, proxy can also use the regular HTTP protocol.Describe the solution you'd like
Inspect scheme of the proxy URI and optionally wrap the base connector with hyper_proxy. Hide it behind a new feature
http_proxy
(name suggestions welcome).Found some past discussions on this:
#1010
#837
Describe alternatives you've considered
None so far
Documentation, Adoption, Migration Strategy
No response
Target crate for feature
kube-client
The text was updated successfully, but these errors were encountered: