try grafana and clickhouse dashboard

chart/values.yaml

@@ -5,4 +5,5 @@ tools:
   - hashicorp-vault
   - crowdsec
   - redis
-  - clickhouse
+  - clickhouse
+  - grafana

grafana/Chart.yaml

@@ -0,0 +1,34 @@
+# Chart: keydb-custom
+# Helm chart tailored for KeyDB (EqAlpha) on 2 Raspberry Pi 5 nodes
+# - Mode: master (statefulset index 0) + replica (index 1)
+# - Replica runs as replicaof master at startup
+# - server-threads = 4
+# - Config mounted via ConfigMap
+# - Liveness / readiness probes included
+# - Persistence via PersistentVolumeClaim (storageClass configurable)
+# -----------------------------------------------------------------------------
+# Chart.yaml
+# -----------------------------------------------------------------------------
+apiVersion: v2
+name: grafana
+description: A Helm chart for Kubernetes
+
+dependencies:
+- name: tool
+  version: 0.1.0
+  repository: https://gitea.arcodange.duckdns.org/api/packages/arcodange-org/helm
+- name: grafana
+  version: 10.3.0
+  repository: https://grafana.github.io/helm-charts
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+version: 0.1.0
+appVersion: "latest"

grafana/templates/helm-chart-config.yaml

@@ -0,0 +1,3 @@
+{{- if eq .Values.tool.kind "HelmChart" -}}
+{{- include "tool.helm-chart-config.tpl" . -}}
+{{- end -}}

grafana/templates/helm-chart.yaml

@@ -0,0 +1,3 @@
+{{- if eq .Values.tool.kind "HelmChart" -}}
+{{- include "tool.helm-chart.tpl" . -}}
+{{- end -}}