5 Commits

Author SHA1 Message Date
Lari Hotari
e6f05809bd
Migrate from kube-prometheus-metrics to victoria-metrics-k8s-stack (#592) 2025-03-08 16:36:41 -08:00
Lari Hotari
4de387e726
Workaround issue with Prometheus 3.0 and metrics (#577)
* Add "fallbackScrapeProtocol: PrometheusText0.0.4" to all pod monitors
2025-03-03 06:26:04 -08:00
lenglet-k
eedc21da30
feat: add metricsRelabelings on podMonitor (#406) 2023-12-21 08:24:49 -08:00
MMeent
c0a8c1b97f
Use the 'pulsar.matchLabels' template for matching components of this chart. (#118)
This also limits the scope of the PodMonitors to the resources of only this install, instead of all installs that share `component:` label values.

Co-authored-by: Matthias van de Meent <matthias.vandemeent@cofano.nl>
2022-01-26 15:38:52 +02:00
Miecio
025b263206
Extend podmonitor and add relabels (#100)
### Motivation

As I wanted to use [streamnative/apache-pulsar-grafana-dashboard](https://github.com/streamnative/apache-pulsar-grafana-dashboard) with this helm chart and own cluster wide Prometheus stack I decided that use of PodMonitor CRD is a good way. Unfortunately prometheus config has some metrics relabelings that are required by grafana dashboard. I decied to port them directly to PodMonitor definition

### Modifications

* Added missing PodMonitor for autorecovery
* Port relabelings from `prometheus-configmap.yaml` to each PodMonitor

### Verifying this change

- [x] Make sure that the change passes the CI checks.
2021-01-30 09:24:21 -08:00