Kilian Ries

I got it running by changing the pip install in the Dockerfile: ```bash # Install Python dependencies from requirements.txt RUN pip install --break-system-packages --no-cache-dir -r requirements.txt ``` The original install...

i added a pull request which should fix the issue; tried it locally - works perfect

@noobHappylife i got it working by deploying a separat `PodMonitor` for the keeper installation: ```bash apiVersion: monitoring.coreos.com/v1 kind: PodMonitor metadata: labels: app.kubernetes.io/instance: clickhouse-operator app.kubernetes.io/name: altinity-clickhouse-operator name: clickhouse-keeper-metrics namespace: clickhouse-operator spec:...

Would be really cool to see this getting merged

@Slach just found this old discussion (https://github.com/Altinity/clickhouse-operator/issues/862) which exactly describes what @jitendra1411 implemented here: https://github.com/Altinity/clickhouse-operator/pull/1798. Do you see a chance to review the PR?

But was introduced with `9.3.5` but already fixed with `9.3.6`, see: https://github.com/grafana/helm-charts/commit/dff3f1062d3c18014eedc9825ce4ec4102a70ab2

@Slach ah i did miss the relabel config ... ok with that it works, correct. However i think this is kind of `outdated` and all other projects these days just...

I provided the corresponding changes and some minor fixes to the test setup itself you recommended ;) I tried it with minikube and all metrics are working now:

@marcofranssen thanks for the hint ;) **Refactor to use generic params.InsertPairs helper function** - Extended ValueType interface to support *int32 pointer type - Replaced manual fmt.Sprint() calls with params.InsertPairs() in...

@cw-Guo done