Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
×

Cluster Observability Operator release notes

The Cluster Observability Operator is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

The Cluster Observability Operator (COO) is an optional OKD Operator that enables administrators to create standalone monitoring stacks that are independently configurable for use by different services and users.

The COO complements the built-in monitoring capabilities of OKD. You can deploy it in parallel with the default platform and user workload monitoring stacks managed by the Cluster Monitoring Operator (CMO).

These release notes track the development of the Cluster Observability Operator in OKD.

The following table provides information about which features are available depending on the version of Cluster Observability Operator and OKD:

COO Version OCP Versions Dashboards Distributed Tracing Logging Troubleshooting Panel

0.2.0

4.11

✔

✘

✘

✘

0.3.0+

4.11 - 4.15

✔

✔

✔

✘

0.3.0+

4.16+

✔

✔

✔

✔

Cluster Observability Operator 0.4.1

The following advisory is available for Cluster Observability Operator 0.4.1:

New features and enhancements

  • You can now configure WebTLS for Prometheus and Alertmanager.

CVEs

Bug fixes

  • Previously, when you deleted the dashboard UI plugin, the consoles.operator.openshift.io resource still contained console-dashboards-plugin. This release resolves the issue. (COO-152)

  • Previously, the web console did not display the correct icon for Red Hat COO . This release resolves the issue. (COO-353)

  • Previously, when you installed the COO from the web console, the support section contained an invalid link. This release resolves the issue. (COO-354)

  • Previously, the cluster service version (CSV) for COO linked to an unofficial version of the documentation. This release resolves the issue. (COO-356)

Cluster Observability Operator 0.4.0

The following advisory is available for Cluster Observability Operator 0.4.0:

New features and enhancements

Troubleshooting UI plugin

  • 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 OKD version 4.17+ can access the troubleshooting UI panel from the Application Launcher app launcher. Alternatively, on versions 4.16+, you can access it in the web console by clicking on Observe → Alerting.

For more information, see troubleshooting UI plugin.

Distributed tracing UI plugin

  • The distributed tracing UI plugin has been enhanced, with a Gantt chart now available for exploring traces.

For more information, see distributed tracing UI plugin.

Bug fixes

  • Previously, metrics were not available to normal users when accessed in the Developer perspective of the web console, by clicking on Observe → Logs. This release resolves the issue. (COO-288)

  • Previously, the troubleshooting UI plugin used the wrong filter for network observability. This release resolves the issue. (COO-299)

  • Previously, the troubleshooting UI plugin generated an incorrect URL for pod label searches. This release resolves the issue. (COO-298)

  • Previously, there was an authorization vulnerability in the Distributed tracing UI plugin. This release resolves the issue and the Distributed tracing UI plugin has been hardened by using only multi-tenant TempoStack and TempoMonolithic instances going forward.

Cluster Observability Operator 0.3.2

The following advisory is available for Cluster Observability Operator 0.3.2:

New features and enhancements

  • With this release, you can now use tolerations and node selectors with MonitoringStack components.

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 OKD. This release resolves the issue. (COO-260)

Cluster Observability Operator 0.3.0

The following advisory is available for Cluster Observability Operator 0.3.0:

New features and enhancements

  • With this release, the Cluster Observability Operator adds backend support for future OKD observability web console UI plugins and observability components.

Cluster Observability Operator 0.2.0

The following advisory is available for Cluster Observability Operator 0.2.0:

New features and enhancements

  • With this release, the Cluster Observability Operator supports installing and managing observability-related plugins for the OKD web console user interface (UI). (COO-58)

Cluster Observability Operator 0.1.3

The following advisory is available for Cluster Observability Operator 0.1.3:

Bug fixes

  • Previously, if you tried to access the Prometheus web user interface (UI) at http://<prometheus_url>:9090/graph, the following error message would display: Error opening React index.html: open web/ui/static/react/index.html: no such file or directory. This release resolves the issue, and the Prometheus web UI now displays correctly. (COO-34)

Cluster Observability Operator 0.1.2

The following advisory is available for Cluster Observability Operator 0.1.2:

CVEs

Bug fixes

  • Previously, certain cluster service version (CSV) annotations were not included in the metadata for COO. Because of these missing annotations, certain COO features and capabilities did not appear in the package manifest or in the OperatorHub user interface. This release adds the missing annotations, thereby resolving this issue. (COO-11)

  • Previously, automatic updates of the COO did not work, and a newer version of the Operator did not automatically replace the older version, even though the newer version was available in OperatorHub. This release resolves the issue. (COO-12)

  • Previously, Thanos Querier only listened for network traffic on port 9090 of 127.0.0.1 (localhost), which resulted in a 502 Bad Gateway error if you tried to reach the Thanos Querier service. With this release, the Thanos Querier configuration has been updated so that the component now listens on the default port (10902), thereby resolving the issue. As a result of this change, you can also now modify the port via server side apply (SSA) and add a proxy chain, if required. (COO-14)

Cluster Observability Operator 0.1.1

The following advisory is available for Cluster Observability Operator 0.1.1:

New features and enhancements

This release updates the Cluster Observability Operator to support installing the Operator in restricted networks or disconnected environments.

Cluster Observability Operator 0.1

This release makes a Technology Preview version of the Cluster Observability Operator available on OperatorHub.