From 02064bc122b93f5db955860e8fbf96e41ebd42b5 Mon Sep 17 00:00:00 2001
From: tomjohntaylor <46534506+tomjohntaylor@users.noreply.github.com>
Date: Wed, 30 Mar 2022 16:00:48 +0200
Subject: [PATCH] Create PrometheusOperatorSyncFailed

---
 .../PrometheusOperatorSyncFailed                | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 content/runbooks/prometheus-operator/PrometheusOperatorSyncFailed

diff --git a/content/runbooks/prometheus-operator/PrometheusOperatorSyncFailed b/content/runbooks/prometheus-operator/PrometheusOperatorSyncFailed
new file mode 100644
index 0000000..e9e3455
--- /dev/null
+++ b/content/runbooks/prometheus-operator/PrometheusOperatorSyncFailed
@@ -0,0 +1,17 @@
+# PrometheusOperatorSyncFailed
+
+## Meaning
+
+There were problems with Prometheus components synchronization that is usually done by prometheus-operator.
+
+## Impact
+
+New changes promoted to prometheus-operator can not be deployed or there could be some problems with auto-healing.
+
+## Diagnosis
+
+Check prometheus-operator pods logs by running, ex. `kubect logs -f <name_of_pod> -n <name_of_namespace>`
+
+## Mitigation
+
+Any fixes in configuration diagnosed by reviewing prometheus-operator logs.