eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

C0: switch grafana deployment to Recreate strategy

Browse source 
Grafana uses an RWO PVC for SQLite + Bleve search index. RollingUpdate
spawns the new pod before terminating the old one, so the new pod
crashloops on the index lock until rollout timeout. Recreate terminates
the old pod first, letting the new pod acquire the lock cleanly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-05-19 06:33:26 -07:00
commit 2fae0f7161
2 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
argocd/manifests/grafana/deployment.yaml
View file

@ -14,7 +14,9 @@ spec:
app.kubernetes.io/name: grafana app.kubernetes.io/name: grafana
app.kubernetes.io/instance: grafana app.kubernetes.io/instance: grafana
strategy: strategy:
type: RollingUpdate # RWO PVC for SQLite + Bleve index — RollingUpdate spawns the new pod
# before the old one terminates, and it crashloops on the index lock.
type: Recreate
template: template:
metadata: metadata:
labels: labels:

1
docs/changelog.d/+grafana-recreate-strategy.infra.md Normal file
View file

@ -0,0 +1 @@
Switched Grafana's deployment strategy from `RollingUpdate` to `Recreate`. With an RWO PVC holding the SQLite database and Bleve search index, `RollingUpdate` reliably crashloops the new pod on the index lock until rollout timeout. `Recreate` terminates the old pod first so the new one acquires the lock cleanly.