From cee0eaeab37ff40ba1e63c12b639c02f73c42be8 Mon Sep 17 00:00:00 2001
From: Nils Stinnesbeck <git@stinnesbeck.com>
Date: Sat, 17 Oct 2026 21:45:56 +0200
Subject: [PATCH] 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
---
 k8s/grafana.yaml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/k8s/grafana.yaml b/k8s/grafana.yaml
index 0032a52..135aa75 100644
--- a/k8s/grafana.yaml
+++ b/k8s/grafana.yaml
@@ -109,12 +109,14 @@ spec:
             periodSeconds: 30
             timeoutSeconds: 5
             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:
             requests:
               cpu: 250m
-              memory: 256Mi
-            limits:
               memory: 512Mi
+            limits:
+              memory: 1Gi
           securityContext:
             allowPrivilegeEscalation: false
             capabilities: