node-exporter: use correct procfs location#2549
Merged
philipgough merged 1 commit intoprometheus-operator:mainfrom May 16, 2025
Merged
node-exporter: use correct procfs location#2549philipgough merged 1 commit intoprometheus-operator:mainfrom
philipgough merged 1 commit intoprometheus-operator:mainfrom
Conversation
this sets the procfs location in node-exporter to /host/root/proc since the host fs is mounted at /host/root Fixes prometheus-operator#2548
simonpasquier
approved these changes
May 16, 2025
philipgough
approved these changes
May 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
this sets the procfs location in node-exporter to /host/root/proc since the host fs is mounted at /host/root
Fixes #2548
Description
As per issue #2548 this changes the configuration of node-exporter so it uses
/host/root/procas the location of the proc fsType of change
What type of changes does your code introduce to the kube-prometheus? Put an
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Changelog entry
Please put a one-line changelog entry below. Later this will be copied to the changelog file.