-
-
Notifications
You must be signed in to change notification settings - Fork 303
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
https socks http connector and rustls now working #1236
Labels
bug
Something isn't working
Comments
for clarification, the problem here is that it works with native-tls but not rustls, right? some things that might get you on track);
|
but still does not work, it complains about:
|
The reason I need a socks5 connector is that my k8s is too old and does not support the proxy settings... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current and expected behavior
Background.:
I am trying to upgrade my kube-rs crate to latest version, for this I need to update from native-tls to rustls
Current behavior:
I am getting an error when trying to build a client based on https<socks> connector, I am not sure why, but I got this working with native tls.
This works:
This does not work:
Expected behavior:
I would expect the code above to work and successfully create a connection to a kubeAPI through socks and https
Possible solution
I don't know of a possible solution, I am writing this because I am adopting one of your examples https://github.com/kube-rs/kube/blob/main/examples/custom_client_tls.rs and so far I have been unsuccessful
Additional context
No response
Environment
I build the kubeconfig dynamically/programatically
I am using vanilla k8s
Configuration and features
and
Affected crates
kube-client
Would you like to work on fixing this bug?
maybe
The text was updated successfully, but these errors were encountered: