From a0628a5dfd740cbdfbedc054eec22eb8e2aaf3ca Mon Sep 17 00:00:00 2001
From: Hector Huertas <hectorhuertas@gmail.com>
Date: Fri, 13 Oct 2023 12:57:39 +0200
Subject: [PATCH] Fix the join on the ContainerOOMing alert

---
 common/container.yaml.tmpl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common/container.yaml.tmpl b/common/container.yaml.tmpl
index d7e759b..f2dc699 100644
--- a/common/container.yaml.tmpl
+++ b/common/container.yaml.tmpl
@@ -27,7 +27,7 @@ groups:
           action: "Investigate CPU consumption and adjust pods resources if needed."
           dashboard: "https://grafana.$ENVIRONMENT.$PROVIDER.uw.systems/d/VAE0wIcik/kubernetes-pod-resources?orgId=1&refresh=1m&from=now-12h&to=now&var-instance=All&var-namespace={{ $labels.namespace }}"
       - alert: ContainerOOMing
-        expr: kube_pod_container_status_last_terminated_reason{reason="OOMKilled"} and on (container) kube_pod_container_status_ready == 0
+        expr: kube_pod_container_status_last_terminated_reason{reason="OOMKilled"} and on (container,pod) kube_pod_container_status_ready == 0
         for: 5m
         annotations:
           summary: "Container {{$labels.namespace}}/{{$labels.pod}}/{{$labels.container}} has been OOMKilled recently and it's not ready"