OBSDOCS-2548 COO 1.3 GA Release Notes

Author: gabriel-rh

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

@@ -26,6 +26,81 @@ The following table provides information about which features are available depe
 
 include::snippets/unified-perspective-web-console.adoc[]
 
+
+[id="cluster-observability-operator-release-notes-1-3_{context}"]
+== {coo-full} 1.3
+
+The following advisory is available for {coo-full} 1.3:
+
+//* link:https://access.redhat.com/errata/RHBA-2025:XXXX[RHBA-2025:XXXX {coo-full} 1.3]
+
+[id="cluster-observability-operator-1-3-new-features-enhancements_{context}"]
+=== New features and enhancements
+
+
+[id="cluster-observability-operator-1-3-bug-fixes_{context}"]
+=== Bug fixes
+
+Troubleshooting panel handles {product-title} 4.19 alert URLs correctly::
+Before this update, {product-title} 4.19 introduced changes to alert URL formatting where some URLs contained only console-internal numeric IDs without alert names. As a consequence, the korrel8r troubleshooting panel failed to process these URLs correctly and could not correlate alerts with related resources.
++
+With this release, korrel8r correctly handles alert URLs from {product-title} 4.19, including URLs that contain only numeric identifiers. As a result, the troubleshooting panel works correctly with all alert types on {product-title} 4.19 clusters.
++
+link:https://issues.redhat.com/browse/COO-1145[COO-1145]
+
+Troubleshooting panel generates valid LogQL queries for Loki logs::
+Before this update, the troubleshooting panel generated malformed LogQL queries when accessing Loki logs through the korrel8r graph. The panel omitted label names from query expressions, producing invalid syntax such as `{ :"value" }` instead of `{label="value"}`. As a consequence, users could not open Loki logs from the korrel8r graph in the {product-title} console and encountered parsing errors from the Observatorium API.
++
+With this release, the troubleshooting panel correctly generates valid LogQL queries with proper label matcher syntax. As a result, users can successfully navigate from the korrel8r graph to corresponding Loki logs for detailed investigation.
++
+link:https://issues.redhat.com/browse/COO-1271[COO-1271]
+
+`UIPlugin` monitoring configuration persists after operator upgrades::
+Before this update, when upgrading the {coo-full} from version 1.2.0 to 1.2.1 or later, the monitoring `UIPlugin` configuration was removed during the upgrade process. The `UIPlugin` spec became empty, showing only the plugin type while losing all configuration details such as {rh-rhacm} integration settings, Perses dashboards, and incident management settings. As a consequence, users could not access monitoring dashboards and features after the upgrade, and the operator logged errors stating `monitoring configuration can not be empty for plugin type Monitoring`.
++
+With this release, the {coo-full} correctly preserves monitoring `UIPlugin` configuration during upgrades. As a result, monitoring dashboards, {rh-rhacm} integration, and incident management features remain available after operator upgrades without requiring manual reconfiguration.
++
+link:https://issues.redhat.com/browse/COO-1051[COO-1051]
+
+Troubleshooting panel navigates to Kubernetes Events page::
+Before this update, clicking on Kubernetes Events in the troubleshooting panel visualization node failed to navigate to the Events page in the {product-title} console. As a consequence, users could not view detailed Kubernetes Event information through the troubleshooting panel workflow and had to manually navigate to the Events page.
++
+With this release, the troubleshooting panel correctly handles navigation to the Kubernetes Events page when users click on event nodes in the visualization. As a result, users can successfully navigate from the troubleshooting panel to view detailed Kubernetes Event information in the console.
++
+link:https://issues.redhat.com/browse/COO-1178[COO-1178]
+
+Troubleshooting panel navigates to VirtualMachine resources correctly::
+Before this update, the troubleshooting panel generated incorrect URLs when navigating to `VirtualMachineInstance` resources from the visualization graph. The panel used an invalid resource path format that did not exist in the {product-title} console. As a consequence, users received 404 errors when clicking on `VirtualMachineInstance` nodes in the troubleshooting panel and could not view virtual machine details.
++
+With this release, the troubleshooting panel generates correct URLs using the proper API group format (`kubevirt.io~v1~VirtualMachine`) when navigating to virtual machine resources. As a result, users can successfully navigate from the troubleshooting panel to view `VirtualMachine` resource details in the console.
++
+link:https://issues.redhat.com/browse/COO-1219[COO-1219]
+
+Korrel8r runs on FIPS-enabled clusters::
+Before this update, the korrel8r binary was not compiled with Federal Information Processing Standards (FIPS) compliant mode enabled. As a consequence, korrel8r pods failed to start on FIPS-enabled clusters and logged the error "FIPS mode is enabled, but this binary is not compiled with FIPS compliant mode enabled."
++
+With this release, the korrel8r container image uses a FIPS-compliant base image and the binary is compiled with FIPS mode enabled. As a result, korrel8r runs successfully on FIPS-enabled {product-title} clusters.
++
+link:https://issues.redhat.com/browse/COO-555[COO-555]
+
+`UIPlugin` status updates correctly in all reconciliation scenarios::
+Before this update, the `UIPlugin` controller did not update the custom resource status field in all reconciliation scenarios. The controller failed to update the status when reconciliation errors occurred, causing the status to report success even when configuration changes were not applied. As a consequence, users could not accurately determine the state of `UIPlugin` resources through the status field and had to check the generation field or operator logs to debug issues.
++
+With this release, the {coo-full} correctly updates `UIPlugin` status in all reconciliation scenarios, including error conditions. As a result, users can rely on the `UIPlugin` status field to accurately reflect the current state of the resource and troubleshoot configuration issues more effectively.
++
+link:https://issues.redhat.com/browse/COO-1055[COO-1055]
+
+Distributed tracing `UIPlugin` handles double quotes in TraceQL queries::
+Before this update, the distributed tracing `UIPlugin` did not properly handle double quotes in TraceQL query expressions. The query parser failed when attribute values contained double quotes, such as regex patterns in HTTP route attributes. As a consequence, users could not query traces with attributes containing double quotes, even when these values were selected from dropdown menus in the user interface.
++
+With this release, the {product-title} distributed tracing console plugin correctly processes TraceQL queries containing double quotes in attribute values. As a result, users can query traces with any attribute values, including those containing special characters like double quotes.
++
+link:https://issues.redhat.com/browse/COO-1175[COO-1175]
+
+[id="cluster-observability-operator-1-3-known-issues_{context}"]
+=== Known issues
+
+
 [id="cluster-observability-operator-release-notes-1-2-2_{context}"]
 == {coo-full} 1.2.2
 
@@ -323,7 +398,7 @@ The following advisory is available for {coo-full} 0.3.2:
 [id="cluster-observability-operator-0-3-2-bug-fixes_{context}"]
 === Bug fixes
 
-* Previously, the logging UIPlugin was not in the `Available` state and the logging pod was not created, when installed on a specific version of {ocp-product-title}.
+* Previously, the logging `UIPlugin` was not in the `Available` state and the logging pod was not created, when installed on a specific version of {ocp-product-title}.
 This release resolves the issue. (link:https://issues.redhat.com/browse/COO-260[*COO-260*])
 
 [id="cluster-observability-operator-release-notes-0-3-0"]