Reload server TLS configuration on the fly #3489
Closed
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
chelseakomlo
changed the title
chelseakomlo
force-pushed
the
f-server-tls-reload
branch
2 times, most recently
from
5314496
to
3230b31
Compare
Reload only the config if agent is already using TLS
lock keyloader before loading/caching a new certificate
chelseakomlo
force-pushed
the
f-server-tls-reload
branch
from
2d78ea5
to
11daaab
Compare
|
Merging with #3492 to track changes in a single PR. |
|
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In order to dynamically move to TLS, we need to completely update a server's TLS configuration, and refresh the server's RPC connections with a new TLS wrapper.
Depends on #3479