From 3a9ad8f9025ea4cdeed782be7cfb6248a16f37ef Mon Sep 17 00:00:00 2001 From: morazow Date: Fri, 13 Feb 2026 16:47:54 +0100 Subject: [PATCH 1/6] [helm] Enable metrics reporting in helm charts --- helm/README.md | 42 ++++ helm/templates/_metrics.tpl | 53 +++++ helm/templates/configmap.yaml | 5 +- helm/templates/svc-coordinator.yaml | 4 + helm/templates/svc-tablet.yaml | 4 + helm/tests/metrics_test.yaml | 195 ++++++++++++++++++ helm/values.yaml | 7 + .../install-deploy/deploying-with-helm.md | 28 +++ 8 files changed, 337 insertions(+), 1 deletion(-) create mode 100644 helm/templates/_metrics.tpl create mode 100644 helm/tests/metrics_test.yaml diff --git a/helm/README.md b/helm/README.md index cd0985f6e4..26b0729327 100644 --- a/helm/README.md +++ b/helm/README.md @@ -93,6 +93,48 @@ Important Fluss options surfaced by the chart: - internal.listener.name: Which listener is used for internal communication (defaults to INTERNAL). - tablet-server.id: Required to be unique per TabletServer. The chart auto‑derives this from the StatefulSet pod ordinal at runtime. +### Metrics and Prometheus scraping + +The chart can enable Fluss metrics reporters and add scrape annotations to Services. + +Example: + +```bash +helm install fluss ./fluss-helm \ + --set metrics.enabled=true +``` + +When enabled, the chart will: +- configure `metrics.reporters` from reporter names in values +- configure `metrics.reporter..