-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[prometheus-smartctl-exporter] Don't use hostNetwork
#4964
Conversation
hostNetwork
hostNetwork
Signed-off-by: GitHub <[email protected]>
Signed-off-by: GitHub <[email protected]>
Depends on if prometheus is inside or outside the k8s network.... I think it probably should be made configurable then, rather then just remove it entirely. |
If Prometheus is inside the cluster then couldn't/shouldn't the exporter be exposed via an ingress (or loadbalancer)? Either way if you think that this should be configurable then I'll switch to that. Maybe best to keep the current default and then just bump a patch version? |
Signed-off-by: Judah Rand <[email protected]>
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. Thanks! :)
ingress would expose them load balanced. You couldn't predictably target all of them for scraping.
hmmm... Yeah, I guess if its a new default, it may be better to bump the minor version, or leave it as a patch version and keep it with the old default. Either way is ok I think. |
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.
Thank you, @judahrand, for your PR. LGTM. I'd consider this change a feature rather than a patch, though.
Signed-off-by: GitHub <[email protected]>
I've updated the PR to bump a minor version instead so I think this should be good to go? |
…unity#4964) * Don't use `hostNetwork` Signed-off-by: GitHub <[email protected]> * Bump chart version Signed-off-by: GitHub <[email protected]> * Make `hostNetwork` configurable Signed-off-by: Judah Rand <[email protected]> * Bump minor version instead Signed-off-by: GitHub <[email protected]> --------- Signed-off-by: GitHub <[email protected]> Signed-off-by: Judah Rand <[email protected]>
What this PR does / why we need it
I can't see any reason that this exporter requires
hostNetwork: true
. It should only be looking at local devices. This also means that issues with port usage can occur when also usingnode-exporter
which does needhostNetwork
. I think it'd be best to just just remove the line as this PR does.Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)Special notes for your reviewer
Checklist
[prometheus-couchdb-exporter]
)