-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
Consider changing default tls stack from openssl-tls
to rustls-tls
#1192
Comments
FWIW I’m moving Aptakube to rustls on the next version. The app is being used in a large variety of environments, but always from outside the cluster. I’ll report back how it goes🤞 |
Have started migration most my controllers to rustls as well this month given a bunch more openssl security vulnerabilities have started surfacing from security scanners, so will make another update next month on how that turned out. |
https://github.com/metalbear-co/mirrord uses kube-rs + rustls and it works great. I think making it the default would be awesome :) |
I forgot about this threqs, but I'm using rustls on Aptakube for the last 3 months and had zero issues reported 👍 |
If the latest mass-closure of rustls issues does not come with any negative side-effects, we should consider finally moving over to
rustls
as a default.Issue comparison
Feature Comparison
Based on above issues; moving now would give us default support for
tls-server-name
.It could also potentially give us a much faster windows ci (experimentation pending) due to how long the openssl install takes.
Cross compilation
Minor point, but the standard glibc based x86_64 linux -> musl x86_64 cross compile technically becomes viable locally without build containers using
cargo build --target x86_64-unknown-linux-musl
(works inversion-rs
which is now usingrustls-tls
).Questions
rustls
overopenssl
that we should take into consideration?The text was updated successfully, but these errors were encountered: