-
Notifications
You must be signed in to change notification settings - Fork 131
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
Reload cert/key for every new conn #927
Conversation
support reload cluster/downstream TLS cert/key. CA still can not be hot-reload now
/run-all-tests |
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Reload cert/key for every new conn support reload cluster/downstream TLS cert/key. CA still can not be hot-reload now * expand the loop
support reload cluster/downstream TLS cert/key.
CA still can not be hot-reload now
What problem does this PR solve?
preliminary of #891
Reload cert/key of tls for new connection
for the pd client and kv client need to update dep version of pd/db, it will be handle by the client.
but this pr enough for reload certification used to connecting downstream db.
What is changed and how it works?
Check List
Tests
Code changes
Side effects
Related changes