-
Notifications
You must be signed in to change notification settings - Fork 12
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
Limit serving of insecure metrics by allowing configurable IP #275
Limit serving of insecure metrics by allowing configurable IP #275
Conversation
ecbe724
to
69b7776
Compare
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.
LGTM
minor comments
the e2e failure is curl failing with error 35 which is SSL connection error: |
ad3d191
to
3370707
Compare
curl being obsolete is unlikely the culprit. Let's add |
3370707
to
e7f52fa
Compare
Ack, will do now. |
cafb1cf
to
2fb3202
Compare
I tried a few things suggested in the link you recommended as well as a few others but didn't have much luck. |
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.
weird that -v
doesn't give us more output, but I think I found the culprit anyway
ba4a620
to
1db2cad
Compare
1db2cad
to
a28c78f
Compare
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.
almost there, let's fix a minor error issue which survived the last round of updates and we can merge (and begin the backport dance)
a28c78f
to
d6d3428
Compare
Currently we are serving insecure metrics on all IPv4 routable addresses on the local machine (0.0.0.0). In this PR, we make the metric IP configurable in order to ensure that we listen for insecure metrics port only on one IP to reduce security vulnerability. Signed-off-by: Swati Sehgal <[email protected]>
Signed-off-by: Swati Sehgal <[email protected]>
d6d3428
to
1042edc
Compare
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.
thanks, LGTM!
Currently we are serving insecure metrics on all IPv4 routable addresses on the local machine (0.0.0.0).
In this PR, we make the metric IP configurable so that in order to ensure that we listen for insecure metrics port only ona configurable IP.