[kube-prometheus-stack] add aws-node exporter #4474
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.
What this PR does / why we need it
Hello, as part of our project to migrate from old prometheus stack deployed independently, we moved to prometheus operator.
Previously we had a job in our config to get metrics from pod aws-node deployed on our EKS cluster.
Instead of declare an additionalScrape config I would like to continue on the new logic (serviceMonitor) to get metrics
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)As part of our project to migrate from old prometheus stack deployed independently, we moved to prometheus operator.
Previously we had a job in our config to get metrics from pod aws-node deployed on our EKS cluster.
Instead of declaring an additionalScrape config I would like to continue on the new logic (serviceMonitor) to get metrics from pods.
Special notes for your reviewer
I've generated manifest and deployed them on my cluster
Then I'm able to query all metrics
Checklist
[prometheus-couchdb-exporter]
)