How can I use socks5 proxy

[Masber]

Dear kube-rs team,

I am learning using your library and rust and I need to access my kubectl through a socks5 proxy. I copied the ~/.kube/config file from remote machine to local and run this

RUST_LOG=trace KUBECONFIG=/home/msopena/kube.config https_proxy=socks5h://localhost:1080 cargo run

and this is my code

use k8s_openapi::api::batch::v1::Job;
use kube::{
    api::{Api, DeleteParams, PostParams},
    runtime::wait::{await_condition, conditions},
    Client,
};

#[tokio::main]
async fn main() -> core::result::Result<(), Box<dyn std::error::Error>> {

    env_logger::init();

    let client = Client::try_default().await?;
    let jobs: Api<Job> = Api::default_namespaced(client);

    let params = kube::api::ListParams::default();
    jobs.list(&params).await?;

    Ok(())
}

My application hangs when trying to get the list of jobs because it is not using the socks5 proxy

[2022-09-19T16:56:25Z DEBUG kube_client::client::builder] HTTP; http.method=GET http.url=https://10.252.1.12:6442/apis/batch/v1/namespaces/default/jobs? otel.name="list" otel.kind="client"
[2022-09-19T16:56:25Z TRACE tracing::span::active] -> HTTP;
[2022-09-19T16:56:25Z DEBUG kube_client::client::builder] requesting
[2022-09-19T16:56:25Z TRACE tracing::span::active] <- HTTP;
[2022-09-19T16:56:25Z TRACE tower::buffer::worker] returning response future
[2022-09-19T16:56:25Z TRACE tower::buffer::worker] worker polling for next message
[2022-09-19T16:56:25Z TRACE tracing::span::active] -> HTTP;
[2022-09-19T16:56:25Z TRACE hyper::client::pool] checkout waiting for idle connection: ("https", 10.252.1.12:6442)
[2022-09-19T16:56:25Z TRACE hyper::client::connect::http] Http::connect; scheme=Some("https"), host=Some("10.252.1.12"), port=Some(Port(6442))
[2022-09-19T16:56:25Z DEBUG hyper::client::connect::http] connecting to 10.252.1.12:6442
[2022-09-19T16:56:25Z TRACE mio::poll] registering event source with poller: token=Token(50331649), interests=READABLE | WRITABLE
[2022-09-19T16:56:25Z TRACE tracing::span::active] <- HTTP;

Version

kube = { version = "0.74.0", features = ["runtime", "derive"] }
k8s-openapi = { version = "0.15.0", features = ["v1_24"] }

Could you please let me know what am I doing wrong?

thank you

[kazk]

Proxies are not supported out of the box at the moment. I was experimenting with it a while ago, but haven't had the time to finish (#837).

For SOCKS5, you should be able to do something like this with a custom client with hyper-socks2:

let mut config = Config::infer().await?;
let connector = {
    let mut http = HttpConnector::new();
    http.enforce_http(false);
    let proxy = hyper_socks2::SocksConnector {
        proxy_addr: Uri::from_static("socks5://localhost:5000"),
        auth: None,
        connector: http,
    };
    let tls = tokio_native_tls::TlsConnector::from(config.native_tls_connector()?);
    hyper_tls::HttpsConnector::from((proxy, tls))
};
let service = ServiceBuilder::new()
    .layer(config.base_uri_layer())
    .service(hyper::Client::builder().build(connector));
let client = Client::new(service, config.default_namespace);

This was working back in February.

For http(s) proxy, I'm hoping hyper-proxy can be used similarly.

Once we figure these out, the default client needs to be updated to use proxies if configured.

[njust]

Config doesn't have a native_tls_connector() method anymore, or what I'm missing here?

[clux]

It's still there, but it's only available with the native-tls feature: https://github.com/kube-rs/kube-rs/blob/master/kube-client/src/client/config_ext.rs#L83-L85

[Masber]

thx @kazk I got something working like the following:

    let mut config = kube::Config::infer().await?;
    let connector = {
        let mut http = HttpConnector::new();
        http.enforce_http(false);
        let proxy = hyper_socks2::SocksConnector {
            proxy_addr: Uri::from_static("socks5://localhost:1080"),
            auth: None,
            connector: http,
        };
        let mut native_tls_builder = native_tls::TlsConnector::builder();
		native_tls_builder.danger_accept_invalid_certs(true);
		native_tls_builder.danger_accept_invalid_hostnames(true);
		native_tls_builder.use_sni(false);

		let native_tls_connector = native_tls_builder.build().unwrap();

        let tls = tokio_native_tls::TlsConnector::from(native_tls_connector);
        hyper_tls::HttpsConnector::from((proxy, tls))
    };
    let service = ServiceBuilder::new()
        .layer(kube::client::ConfigExt::base_uri_layer(&config))
        .service(hyper::Client::builder().build(connector));
    let client = kube::Client::new(service, config.default_namespace);
        // let client = Client::try_default().await?;
    let jobs: Api<Job> = Api::default_namespaced(client);

    let params = kube::api::ListParams::default();
    jobs.list(&params).await?;

[kazk]

You can add use kube::client::ConfigExt; to get the extension methods like config.base_uri_layer().
If you have native-tls feature enabled, config.native_tls_connector()? returns the TlsConnector based on your kubeconfig.