From b843b704693f00d4de9f6024a2e117f2864c960b Mon Sep 17 00:00:00 2001
From: muralisankuri <87978717+muralisankuri@users.noreply.github.com>
Date: Fri, 23 Feb 2024 11:20:19 +0530
Subject: [PATCH] Create kubernates-pod-oom-killed-alert

---
 .../alertmanager/kubernates-pod-oom-killed-alert      | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 content/runbooks/alertmanager/kubernates-pod-oom-killed-alert

diff --git a/content/runbooks/alertmanager/kubernates-pod-oom-killed-alert b/content/runbooks/alertmanager/kubernates-pod-oom-killed-alert
new file mode 100644
index 0000000..58af821
--- /dev/null
+++ b/content/runbooks/alertmanager/kubernates-pod-oom-killed-alert
@@ -0,0 +1,11 @@
+# PodOOMKilledAlert
+
+## Meaning
+
+This alert is based on an alerting when the pods gets restarted due to the reason OOM Killed
+
+<details>
+<summary>OOM Killed</summary>
+* Pods will gets restrated with many reasons. One of them would be the OOM Killed.
+* OOM Killed :  It occurs when there is a shortage of memory in the Pod to process the messages or task.
+</details>