Resolve cluster alias for opened remote connections #92584
Merged
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
n1v0lg
added
>non-issue
:Distributed Coordination/Network
elasticsearchmachine
added
Team:Distributed (Obsolete)
|
Pinging @elastic/es-security (Team:Security) |
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
Build failure unrelated and tracked here: #92930 |
|
@elasticsearchmachine run elasticsearch-ci/part-2-fips |
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.
#91724 introduced the ability to resolve the cluster alias, given a connection towards a remote cluster. This works for connections obtained via
RemoteConnectionManager::getConnection. However, connections can also be initiated viaopenConnection(e.g., inSniffConnectionStrategy). This PR adds support to correctly resolve the cluster alias for such connections, by wrapping them in anInternalRemoteConnectioninstance. This is necessary to support the new remote cluster security model.