eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/how-to/grafana/upgrade-grafana.md
Erich Blume 5ddb47de1c Review upgrade-grafana doc: fix image tag ref, add sidecar link 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-04 07:53:22 -08:00

1.7 KiB
Raw Blame History

title requires modified last-reviewed tags
Upgrade Grafana
kustomize-grafana-deployment
build-grafana-container
2026-03-04 2026-03-04
how-to
grafana
observability

Upgrade Grafana

Upgraded Grafana from 11.4.0 (Helm chart) to 12.3.3, converting from Helm to Kustomize with a home-built container image.

What Changed

  • Image: docker.io/grafana/grafana:11.4.0 → registry.ops.eblu.me/blumeops/grafana (tagged via Kustomize images: overlay)
  • Deployment: Helm multi-source (chart + values) → single Kustomize directory
  • ArgoCD app: Simplified to one source pointing at argocd/manifests/grafana/

All existing datasources (prometheus, loki, TeslaMate), dashboard ConfigMaps, and Authentik OIDC were preserved without changes.

Grafana 12 Breaking Changes

None affected us:

  • Angular plugin removal — our dashboards already used React panels
  • Datasource UID format enforcement — our UIDs were already compliant
  • Annotation table migration — completed automatically on the small SQLite DB

How to Repeat

To upgrade Grafana again in the future:

  1. Update CONTAINER_APP_VERSION in containers/grafana/Dockerfile
  2. Build and push via mise run container-build-and-release grafana
  3. Update the image tag in argocd/manifests/grafana/kustomization.yaml (under images:)
  4. Update service-versions.yaml
  5. Sync: argocd app sync grafana

The SQLite PVC is disposable — dashboards come from ConfigMaps and datasources from config.

Related