Add SSL/TLS info to "clustering" listener (backport #15399)#15403
Merged
michaelklishin merged 1 commit intov4.2.xfrom Feb 5, 2026
Merged
Add SSL/TLS info to "clustering" listener (backport #15399)#15403michaelklishin merged 1 commit intov4.2.xfrom
michaelklishin merged 1 commit intov4.2.xfrom
Conversation
In the "Listening ports" section of the Management UI and in the /api/overview, the clustering listener was reported as not using TLS, even when it was, because clustering TLS is configured differently than it is for regular listeners. With this change, we properly mark the SSL/TLS status in the Management UI and report the protocol as "clustering/ssl" in Management UI/API. (cherry picked from commit f646b99)
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
2 participants
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 the "Listening ports" section of the Management UI and in the /api/overview, the clustering listener was reported as not using TLS, even when it was, because clustering TLS is configured differently than it is for regular listeners.
With this change, we properly mark the SSL/TLS status in the Management UI and report the protocol as "clustering/ssl" in Management UI/API.
With this change, we can see that status correctly:
This is an automatic backport of pull request #15399 done by [Mergify](https://mergify.com).