OBSDOCS-1876 fix for oom on upgrade

Author: gabriel-rh

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

@@ -13,6 +13,30 @@ The {coo-short} complements the built-in monitoring capabilities of {product-tit
 
 These release notes track the development of the {coo-full} in {product-title}.
 
+The following table provides information about which features are available depending on the version of {coo-full} and {product-title}:
+
+[cols="1,1,1,1,1,1,1", options="header"]
+|===
+| COO Version   | OCP Versions       | Distributed tracing   | Logging   | Troubleshooting panel | ACM alerts | Incident detection
+| 1.1+          | 4.12 - 4.14        | ✔                     | ✔         | ✘                     | ✘          | ✘
+| 1.1+          | 4.15               | ✔                     | ✔         | ✘                     | ✔          | ✘
+| 1.1+          | 4.16 - 4.17        | ✔                     | ✔         | ✔                     | ✔          | ✘
+| 1.1+          | 4.18+              | ✔                     | ✔         | ✔                     | ✔          | ✔
+|===
+
+[id="cluster-observability-operator-release-notes-1-1-1_{context}"]
+== {coo-full} 1.1.1
+
+// Back fill advisory when it is created by KOnflux
+// The following advisory is available for {coo-full} 1.1.1:
+//
+// * link:https://access.redhat.com/errata/RHSA-2025:????[RHEA-2025:??? {coo-full} 1.1.1]
+
+
+[id="cluster-observability-operator-1-1-1-bug-fixes_{context}"]
+=== Bug fixes
+
+* Previously, `observability-operator` and `perses-operator` pods on many clusters entered a `CrashLoopBackOff` state due to `OutOfMemory` errors, after upgrading from {coo-full} 1.0. This release resolves the issue. (link:https://issues.redhat.com/browse/COO-784[*COO-784*])
 
 [id="cluster-observability-operator-release-notes-1-1_{context}"]
 == {coo-full} 1.1
@@ -23,25 +47,17 @@ These release notes track the development of the {coo-full} in {product-title}.
 // * link:https://access.redhat.com/errata/RHSA-2025:????[RHEA-2025:??? {coo-full} 1.1]
 
 
+
 [id="cluster-observability-operator-1-1-new-features-enhancements_{context}"]
 === New features and enhancements
- 
+
 * You can now install the monitoring UI plugin using {coo-short}. (link:https://issues.redhat.com/browse/COO-262[*COO-262*])
 
 * You can enable incident detection in the monitoring UI plugin. (link:https://issues.redhat.com/browse/COO-690[*COO-690*])
 
 * TLS support for the Thanos web endpoint has been added. (link:https://issues.redhat.com/browse/COO-222[*COO-222*])
 
-The following table provides information about which features are available depending on the version of {coo-full} and {product-title}:
 
-[cols="1,1,1,1,1,1,1", options="header"]
-|===
-| COO Version   | OCP Versions       | Distributed tracing   | Logging   | Troubleshooting panel | ACM alerts | Incident detection
-| 1.1           | 4.12 - 4.14        | ✔                     | ✔         | ✘                     | ✘          | ✘
-| 1.1           | 4.15               | ✔                     | ✔         | ✘                     | ✔          | ✘
-| 1.1           | 4.16 - 4.17        | ✔                     | ✔         | ✔                     | ✔          | ✘
-| 1.1           | 4.18+              | ✔                     | ✔         | ✔                     | ✔          | ✔
-|===
 
 [id="cluster-observability-operator-1-1-known-issues_{context}"]
 == Known issues
@@ -88,7 +104,7 @@ This issue is being tracked in link:https://issues.redhat.com/browse/COO-784[*CO
 
 * You can now configure the Alertmanager `scheme` and `tlsConfig` fields in the Prometheus CR. (link:https://issues.redhat.com/browse/COO-219[*COO-219*])
 
-// Dev preview so cannot document 
+// Dev preview so cannot document
 //* You can now install the Monitoring UI plugin using {coo-short}. (link:https://issues.redhat.com/browse/COO-262[*COO-262*])
 
 * The extended Technical Preview for the troubleshooting panel adds support for correlating traces with Kubernetes resources and directly with other observable signals including logs, alerts, metrics, and network events. (link:https://issues.redhat.com/browse/COO-450[*COO-450*])
@@ -129,9 +145,9 @@ The following table provides information about which features are available depe
 |===
 | COO Version    | OCP Versions       | Dashboards   | Distributed Tracing   | Logging   | Troubleshooting Panel
 
-| 0.2.0          | 4.11               | ✔            | ✘                     | ✘         | ✘ 
-| 0.3.0+, 0.4.0+ | 4.11 - 4.15        | ✔            | ✔                     | ✔         | ✘ 
-| 0.3.0+, 0.4.0+ | 4.16+              | ✔            | ✔                     | ✔         | ✔ 
+| 0.2.0          | 4.11               | ✔            | ✘                     | ✘         | ✘
+| 0.3.0+, 0.4.0+ | 4.11 - 4.15        | ✔            | ✔                     | ✔         | ✘
+| 0.3.0+, 0.4.0+ | 4.16+              | ✔            | ✔                     | ✔         | ✔
 |===
 
 [id="cluster-observability-operator-release-notes-0-4-1_{context}"]
@@ -180,7 +196,7 @@ The following advisory is available for {coo-full} 0.4.0:
 
 * The troubleshooting UI panel has been improved so you can now select and focus on a specific starting signal.
 * There is more visibility into Korrel8r queries, with the option of selecting the depth.
-* Users of {product-title} version 4.17+ can access the troubleshooting UI panel from the Application Launcher {launch}. Alternatively, on versions 4.16+, you can access it in the web console by clicking on **Observe** -> **Alerting**.   
+* Users of {product-title} version 4.17+ can access the troubleshooting UI panel from the Application Launcher {launch}. Alternatively, on versions 4.16+, you can access it in the web console by clicking on **Observe** -> **Alerting**.
 
 For more information, see xref:../../observability/cluster_observability_operator/ui_plugins/troubleshooting-ui-plugin.adoc#troubleshooting-ui-plugin[troubleshooting UI plugin].