Skip to content

Add SSL/TLS info to "clustering" listener#15399

Merged
michaelklishin merged 1 commit intomainfrom
clustering-tls-check
Feb 5, 2026
Merged

Add SSL/TLS info to "clustering" listener#15399
michaelklishin merged 1 commit intomainfrom
clustering-tls-check

Conversation

@mkuratczyk
Copy link
Copy Markdown
Contributor

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:
Screenshot 2026-02-05 at 13 12 14

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.
@mkuratczyk mkuratczyk force-pushed the clustering-tls-check branch from 3c72ac8 to f646b99 Compare February 5, 2026 15:29
@michaelklishin michaelklishin self-requested a review February 5, 2026 16:53
@michaelklishin michaelklishin added this to the 4.3.0 milestone Feb 5, 2026
@michaelklishin michaelklishin merged commit 93220ec into main Feb 5, 2026
566 of 575 checks passed
@michaelklishin michaelklishin deleted the clustering-tls-check branch February 5, 2026 17:11
michaelklishin added a commit that referenced this pull request Feb 5, 2026
Add SSL/TLS info to "clustering" listener (backport #15399)
mkuratczyk added a commit that referenced this pull request Feb 6, 2026
follow-up to #15399

the initial PR solved the problem for the Management UI and API,
but we also report listeners in the CLI. This change addresses
this part.
mergify bot pushed a commit that referenced this pull request Feb 6, 2026
follow-up to #15399

the initial PR solved the problem for the Management UI and API,
but we also report listeners in the CLI. This change addresses
this part.

(cherry picked from commit 97c00a3)
mkuratczyk added a commit that referenced this pull request Feb 6, 2026
follow-up to #15399

the initial PR solved the problem for the Management UI and API,
but we also report listeners in the CLI. This change addresses
this part.

(cherry picked from commit 97c00a3)

Co-authored-by: Michal Kuratczyk <michal.kuratczyk@broadcom.com>
michaelklishin pushed a commit that referenced this pull request Feb 7, 2026
follow-up to #15399

the initial PR solved the problem for the Management UI and API,
but we also report listeners in the CLI. This change addresses
this part.
michaelklishin pushed a commit that referenced this pull request Feb 24, 2026
follow-up to #15399

the initial PR solved the problem for the Management UI and API,
but we also report listeners in the CLI. This change addresses
this part.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants