New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: conditionally change hubble-relay port in hubble-ui #16511
fix: conditionally change hubble-relay port in hubble-ui #16511
Conversation
In case of enabled TLS for Hubble Relay the hubble-ui shall follow the service port change Fixes #16510 Signed-off-by: Alex Szakaly <alex.szakaly@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please not that the UI does not yet support connecting to Relay via mTLS. While this change by itself will be eventually needed, it is not sufficient to run UI with Values.hubble.relay.tls.server.enabled=true
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What @gandro mentioned is indeed valid and something to keep in mind. However, as of now, users enabling TLS for Hubble Relay will already notice that the Hubble UI will stop working when doing so. With this change however, the error might be more clear as the connection should fail with a TLS error instead of timing out. TLDR: I think this is OK to merge even though Hubble UI does not yet support TLS.
Given that Hubble UI is not deployed anywhere in our CI, a full CI run is unnecessary. As this PR got all required approvals from the various teams, marking as ready to merge. |
In case of enabled TLS for Hubble Relay the hubble-ui
shall follow the service port change
Signed-off-by: Alex Szakaly alex.szakaly@gmail.com
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: #16510