Kustomize Grafana Deployment
Grafana is deployed via plain Kustomize manifests in argocd/manifests/grafana-ringtail/,
replacing the previous Helm chart. Dashboards, the Tailscale ingress, and the
ExternalSecrets live in the companion argocd/manifests/grafana-config-ringtail/
dir (the two dirs are separate ArgoCD apps: grafana-ringtail and
grafana-config-ringtail).
Manifest Structure
| File | Purpose |
|---|---|
kustomization.yaml | Resource list + configMapGenerator for config files |
deployment.yaml | Grafana container + home-built k8s-sidecar for dashboards |
service.yaml | ClusterIP on port 80 → 3000 |
pvc.yaml | 1Gi SQLite storage |
grafana.ini | Grafana server configuration (fed to configMapGenerator) |
datasources.yaml | Datasource provisioning (fed to configMapGenerator) |
alerting.yaml | Alerting config (fed to configMapGenerator) |
provider.yaml | Dashboard provider config (fed to configMapGenerator) |
serviceaccount.yaml | Service account |
rbac.yaml | ClusterRole/RoleBinding for sidecar ConfigMap access |
Key Details
- PVC name must remain
grafana— changing it would create a new volume and lose the SQLite DB - Sidecar watches ConfigMaps with label
grafana_dashboard=1and reloads dashboards via the Grafana API - Secrets come from ExternalSecrets (
grafana-admin,grafana-authentik-oauth,grafana-teslamate-datasource) managed by thegrafana-config-ringtailArgoCD app
Related
- build-grafana-images — Home-built container images
- grafana — Service reference card