rhobs / rhobs/observability-operator
Accessing kube-state-metrics in a Specific Namespace with MonitoringStack
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 51
- Forks
- 90
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 22
Description
Hello,
I’m currently using the Cluster Observability Operator to create a MonitoringStack in my specific namespace. When I navigate to Developer > Observe, I can write PromQL queries and see all the “kube” labels. However, I would like to scrape these metrics using my own instance of Prometheus, which is deployed by the MonitoringStack.
As I understand it, kube-state-metrics is deployed in the openshift-monitoring namespace and provides provides metrics to all namespaces, but only on GUI. My question is, how can I access these metrics in Prometheus within my own namespace? I’m trying to avoid deploying additional instances of kube-state-metrics in each namespace.
Any guidance or suggestions would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing how MonitoringStack exposes Prometheus targets and kube-state-metrics across namespaces; done would be a supported, documented way to query those metrics from a namespace-local Prometheus without deploying another kube-state-metrics instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100