config: reload tikv/tidb cluster tls for every new established conn (#14833) #15163
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/run-all-tests |
sre-bot
added
component/tikv
security
|
LGTM |
tiancaiamao
approved these changes
Mar 10, 2020
zz-jason
added
the
status/can-merge
|
/run-all-tests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #14833 to release-3.1
What problem does this PR solve?
support reload cluster TLS cert/key file used by TiKV or TiDB-self(CA still can not be hot-reload now)
pd's cert/key will be handled by new pdclient
What is changed and how it works?
reload TLS for every new connection(include grpc auto retry in resetTransport) like etcd
Check List
Tests
Code changes
Side effects
Related changes
Release note
This change is