-
-
Notifications
You must be signed in to change notification settings - Fork 325
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
Optional rustls support #66
Comments
Yeah, I would be very happy to have |
@jnicholls I've tried following your plan in #114 using some of @ctron 's linked commit (ty). Unfortunately, have not been able to make it communicate with a cluster yet (just getting 403s back). My pem input + cert bundles all seem sensible afaikt, but have very little knowledge in this area. Any help to make this work would be appreciated. |
@clux Thanks for jumping into this! You are amazing for creating and supporting this great library and just wanted to start with a big thank you. This afternoon I will find some time to jump in here and see if I can lend a hand! |
Appreciate that! Just a heads up that the rustls issue is actually more or less resolved! Just need to tidy it up a bit for a release and port the oauth module. Any more of the help that you've already jump on or want to jump on is still very much appreciated though! |
Initial support in master. Will release a version with it soon. But it's probably not usable for gke yet: see #120 |
Released in 0.25.0 along with a great pr to help #120 |
Some Rust users in the community are not interested in having OpenSSL as a dependency. Especially just for the support of loading certificate/key data from kubeconfig files.
reqwest
already supportsrustls
as an optional feature instead of usingnative-tls
. You would simply need to switch the cert/key loading to only use reqwest Certificate/Identity APIs, and potentially rustls::internal::pemfile if necessary, rather than the openssl crate.The text was updated successfully, but these errors were encountered: