-
-
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
rustls support #114
rustls support #114
Conversation
Ok. I'm definitely doing client certs wrong. Not sure how to convert the client cert + client key data (from kube config) into a reqwest::Identity atm. But we are pretty close - despite having commented out a few non-standard features. |
or, maybe I am. but something is definitely not working. getting 403s across the board. been debugging with: NAMESPACE=dev cargo run --example pod_informer --no-default-features --features=openapi,native-tls
NAMESPACE=dev cargo run --example pod_informer --no-default-features --features=openapi,rustls-tls with diff --git examples/pod_informer.rs examples/pod_informer.rs
index d5aef09e..9719cfd3 100644
--- examples/pod_informer.rs
+++ examples/pod_informer.rs
@@ -12,7 +12,7 @@ type Pod = Object<PodSpec, PodStatus>;
#[tokio::main]
async fn main() -> anyhow::Result<()> {
- env::set_var("RUST_LOG", "info,kube=trace");
+ env::set_var("RUST_LOG", "debug,reqwest=trace,kube=trace");
env_logger::init();
let config = config::load_kube_config().await?;
let client = APIClient::new(config); and seeing how far it gets.. so far 403 on first GET response in the Informer. |
omg, i accidentally pulled in default-tls...
Did a merge with master, then noticed this... ..This branch actually works after the one-line change in |
basic support is there - works with my clusters, but probably some dragons in here. |
for #66 - trying to learn the crypto stuff to do this properly.
if anyone's reading this and see any obvious mistakes, please call out :-)