Logging is provided as an installable component, with a distinct release cycle from the core OKD. The Red Hat OpenShift Container Platform Life Cycle Policy outlines release compatibility. |
The |
This release includes: OpenShift Logging Bug Fix Release 5.7.1.
Before this update, the presence of numerous noisy messages within the Cluster Logging Operator pod logs caused reduced log readability, and increased difficulty in identifying important system events. With this update, the issue is resolved by significantly reducing the noisy messages within Cluster Logging Operator pod logs. (LOG-3482)
Before this update, the API server would reset the value for the CollectorSpec.Type
field to vector
, even when the custom resource used a different value. This update removes the default for the CollectorSpec.Type
field to restore the previous behavior. (LOG-4086)
Before this update, a time range could not be selected in the OKD web console by clicking and dragging over the logs histogram. With this update, clicking and dragging can be used to successfully select a time range. (LOG-4501)
Before this update, clicking on the Show Resources link in the OKD web console did not produce any effect. With this update, the issue is resolved by fixing the functionality of the "Show Resources" link to toggle the display of resources for each log entry. (LOG-3218)
This release includes OpenShift Logging Bug Fix Release 5.7.0.
With this update, you can enable logging to detect multi-line exceptions and reassemble them into a single log entry.
To enable logging to detect multi-line exceptions and reassemble them into a single log entry, ensure that the ClusterLogForwarder
Custom Resource (CR) contains a detectMultilineErrors
field, with a value of true
.
Before this update, the nodeSelector
attribute for the Gateway component of the LokiStack did not impact node scheduling. With this update, the nodeSelector
attribute works as expected. (LOG-3713)