OBSDOCS-1753 Add known issue with upgrade oom error

Author: gabriel-rh

observability/cluster_observability_operator/cluster-observability-operator-release-notes.adoc

@@ -43,6 +43,17 @@ The following table provides information about which features are available depe
 | 1.1           | 4.18+              | ✔                     | ✔         | ✔                     | ✔          | ✔
 |===
 
+[id="cluster-observability-operator-1-1-known-issues_{context}"]
+== Known issues
+
+These are the known issues in {coo-full} 1.1.0:
+
+* `observability-operator` and `perses-operator` pods enter a `CrashLoopBackOff` state due to `OutOfMemory` errors, after upgrading from {coo-full} 1.0.
++
+A workaround is provided in the knowledge base article link:https://access.redhat.com/solutions/7113898[ClusterObservability and perses operator pod in CrashLoopBackOff due to OOMKilled in RHOCP4].
++
+This issue is being tracked in link:https://issues.redhat.com/browse/COO-784[*COO-784*].
+
 
 [id="cluster-observability-operator-1-1-bug-fixes_{context}"]
 === Bug fixes