Viktor Barzin a02782d11f fix(monitoring): tempo OOMKilled — move resources under tempo.resources ... 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 <noreply@anthropic.com>		2026-06-22 06:44:31 +00:00
..
monitoring	fix(monitoring): tempo OOMKilled — move resources under tempo.resources	2026-06-22 06:44:31 +00:00