From a02782d11fae79f94cd1b8c73266fb18071b2293 Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Mon, 22 Jun 2026 06:44:31 +0000 Subject: [PATCH] =?UTF-8?q?fix(monitoring):=20tempo=20OOMKilled=20?= =?UTF-8?q?=E2=80=94=20move=20resources=20under=20tempo.resources?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pipeline #315 failed: tempo-0 CrashLoopBackOff / OOMKilled (exit 137). The single-binary grafana/tempo chart (v1.24.4) takes container resources at tempo.resources, not a top-level resources: — so my block was ignored and the pod fell to the namespace LimitRange default and OOMed. Set tempo.resources explicitly (req 256Mi / limit 2Gi). tripit + existing monitoring were unaffected throughout. Co-Authored-By: Claude Opus 4.8 --- stacks/monitoring/modules/monitoring/tempo.yaml | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/stacks/monitoring/modules/monitoring/tempo.yaml b/stacks/monitoring/modules/monitoring/tempo.yaml index b3132fab..ae6f63bc 100644 --- a/stacks/monitoring/modules/monitoring/tempo.yaml +++ b/stacks/monitoring/modules/monitoring/tempo.yaml @@ -22,15 +22,17 @@ tempo: # Tempo query/HTTP API — the Grafana datasource URL targets this (3100). server: http_listen_port: 3100 + # Container resources — the single-binary chart key is tempo.resources (NOT a + # top-level `resources:`). With it mis-placed the pod fell to the namespace + # LimitRange default and was OOMKilled (exit 137); set it explicitly here. + resources: + requests: + cpu: 100m + memory: 256Mi + limits: + memory: 2Gi persistence: enabled: true size: 20Gi storageClassName: proxmox-lvm - -resources: - requests: - cpu: 100m - memory: 256Mi - limits: - memory: 1Gi