-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
Provide TLS 1.3 support for 3.5. #15436
Comments
Makes sense to me. Please feel free to deliver a PR, thx |
Initial backport pr merged and docs pr open here etcd-io/website#650. I will raise pr for 3.5.8 changelog shortly, quick question @ahrtr the change touches several aspects of the codebase, do you want just one section updated in the changelog, or under all impacted? /assign |
NO strong opinion on this. Only adding changelog item for etcdserver seems OK to me. Please backport the PR to 3.4 as well if you have bandwitdh, and after changelog for both 3.5 and 3.4 afterwards. thx. |
What would you like to be added?
TLS 1.3 support was (re-)added to the main branch in #15156
... thus resolving #13506
However, organizations running etcd 3.4 and 3.5 are starting to require TLS 1.3 for security compliance.
The "3.4 version" analogue issue: #15437
Why is this needed?
As stated above, organizations running etcd 3.4 and 3.5 are starting to require TLS 1.3 for security compliance. Also, waiting for etcd 3.6 is not compatible with their timelines.
The text was updated successfully, but these errors were encountered: