-
Notifications
You must be signed in to change notification settings - Fork 63
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
Make blackbox-exporter launcher a clickable link #289
Make blackbox-exporter launcher a clickable link #289
Conversation
This PR makes the output of the `blackbox-exporter` launcher script output a clickable link in the style of the `cluster-console` script. Signed-off-by: Chris Collins <collins.christopher@gmail.com>
37f3468
to
ede9d3a
Compare
Replaces the `0.0.0.0` with `127.0.0.1` in the blackbox-exporter output. This does not functionally change anything, but matches the external expectations that 127.0.0.1 is the port in use, to avoid confusion. The internal address for the port forward has to be 0.0.0.0 or it will be unavailable outside of the container. However, the external port map is still 127.0.0.1, and only available on the local machine, whether accessed via 127.0.0.1 or 0.0.0.0 in the browser. Signed-off-by: Chris Collins <collins.christopher@gmail.com>
/retest |
Nice! Thanks Chris!
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clcollins, rendhalver The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
The builds look to be failing on the gpg key for the gcloud-sdk repo. |
/retest |
This PR makes the output of the
blackbox-exporter
launcher scriptoutput a clickable link in the style of the
cluster-console
script.Signed-off-by: Chris Collins collins.christopher@gmail.com