Grafana: memory request 512Mi, limit 1Gi

It runs at about 406 MiB in the cluster, too close to the 512Mi limit:
long-range dashboard queries could get it OOM-killed. The request now
matches what it uses, so the scheduler reserves it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QLJfZQZeAKAwSqViTmLzki
This commit is contained in:
2026-10-17 21:45:56 +02:00
co-authored by Claude Opus 5.5
parent 756ae65d0b
commit cee0eaeab3
+4 -2
View File
@@ -109,12 +109,14 @@ spec:
periodSeconds: 30 periodSeconds: 30
timeoutSeconds: 5 timeoutSeconds: 5
failureThreshold: 3 failureThreshold: 3
# About 406 MiB in steady state in the cluster: request what it uses, and leave room
# for long-range dashboard queries before the limit OOM-kills it.
resources: resources:
requests: requests:
cpu: 250m cpu: 250m
memory: 256Mi
limits:
memory: 512Mi memory: 512Mi
limits:
memory: 1Gi
securityContext: securityContext:
allowPrivilegeEscalation: false allowPrivilegeEscalation: false
capabilities: capabilities: