RATIS-2634. Add TLS support for Netty RPC transport - #1541
Draft
spacemonkd wants to merge 1 commit into
Draft
Conversation
spacemonkd
marked this pull request as draft
August 2, 2026 11:07
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
RATIS-2634. Add TLS support for Netty RPC transport
Netty RPC - both server-to-server (NettyRpcService, NettyRpcProxy) and client-to-server (NettyClientRpc), has no TLS.
The channel pipelines add only protobuf codecs and handlers, never an SslHandler. Only the gRPC transport and the Netty data-stream path support TLS today.
We are mirroring the behaviour in
NettyServerStreamRpc/NettyClientStreamRpcto introduce TLS in this patch.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/RATIS-2634
How was this patch tested?
Patch was tested via unit tests