diff --git a/logging/cluster-logging-release-notes.adoc b/logging/cluster-logging-release-notes.adoc index 4e19ff8c80..234d42f6f6 100644 --- a/logging/cluster-logging-release-notes.adoc +++ b/logging/cluster-logging-release-notes.adoc @@ -11,6 +11,8 @@ toc::[] .Logging Compatibility The {logging-title} is provided as an installable component, with a distinct release cycle from the core {product-title}. The link:https://access.redhat.com/support/policy/updates/openshift#logging[Red Hat OpenShift Container Platform Life Cycle Policy] outlines release compatibility. +include::modules/cluster-logging-rn-5.5.5.adoc[leveloffset=+1] + include::modules/cluster-logging-rn-5.5.4.adoc[leveloffset=+1] include::modules/cluster-logging-rn-5.5.3.adoc[leveloffset=+1] diff --git a/modules/cluster-logging-rn-5.5.5.adoc b/modules/cluster-logging-rn-5.5.5.adoc new file mode 100644 index 0000000000..e7314fb418 --- /dev/null +++ b/modules/cluster-logging-rn-5.5.5.adoc @@ -0,0 +1,93 @@ +//module included in cluster-logging-release-notes.adoc +:_content-type: REFERENCE +[id="cluster-logging-release-notes-5-5-5_{context}"] += Logging 5.5.5 +This release includes link:https://access.redhat.com/errata/RHSA-2022:8781[OpenShift Logging Bug Fix Release 5.5.5]. + +[id="openshift-logging-5-5-5-bug-fixes"] +== Bug fixes +* Before this update, Kibana had a fixed `24h` OAuth cookie expiration time, which resulted in 401 errors in Kibana whenever the `accessTokenInactivityTimeout` field was set to a value lower than `24h`. With this update, Kibana's OAuth cookie expiration time synchronizes to the `accessTokenInactivityTimeout`, with a default value of `24h`. (link:https://issues.redhat.com/browse/LOG-3305[LOG-3305]) + +* Before this update, Vector parsed the message field when JSON parsing was enabled without also defining `structuredTypeKey` or `structuredTypeName` values. With this update, a value is required for either `structuredTypeKey` or `structuredTypeName` when writing structured logs to Elasticsearch. (link:https://issues.redhat.com/browse/LOG-3284[LOG-3284]) + +* Before this update, the `FluentdQueueLengthIncreasing` alert could fail to fire when there was a cardinality issue with the set of labels returned from this alert expression. This update reduces labels to only include those required for the alert. (https://issues.redhat.com/browse/LOG-3226[LOG-3226]) + +* Before this update, Loki did not have support to reach an external storage in a disconnected cluster. With this update, proxy environment variables and proxy trusted CA bundles are included in the container image to support these connections. (link:https://issues.redhat.com/browse/LOG-2860[LOG-2860]) + +* Before this update, {product-title} web console users could not choose the `ConfigMap` object that includes the CA certificate for Loki, causing pods to operate without the CA. With this update, web console users can select the config map, resolving the issue. (link:https://issues.redhat.com/browse/LOG-3310[LOG-3310]) + +* Before this update, the CA key was used as volume name for mounting the CA into Loki, causing error states when the CA Key included non-conforming characters (such as dots). With this update, the volume name is standardized to an internal string which resolves the issue. (link:https://issues.redhat.com/browse/LOG-3332[LOG-3332]) + +[id="openshift-logging-5-5-5-CVEs"] +== CVEs +* link:https://access.redhat.com/security/cve/CVE-2016-3709[CVE-2016-3709] +* link:https://access.redhat.com/security/cve/CVE-2020-35525[CVE-2020-35525] +* link:https://access.redhat.com/security/cve/CVE-2020-35527[CVE-2020-35527] +* link:https://access.redhat.com/security/cve/CVE-2020-36516[CVE-2020-36516] +* link:https://access.redhat.com/security/cve/CVE-2020-36558[CVE-2020-36558] +* link:https://access.redhat.com/security/cve/CVE-2021-3640[CVE-2021-3640] +* link:https://access.redhat.com/security/cve/CVE-2021-30002[CVE-2021-30002] +* link:https://access.redhat.com/security/cve/CVE-2022-0168[CVE-2022-0168] +* link:https://access.redhat.com/security/cve/CVE-2022-0561[CVE-2022-0561] +* link:https://access.redhat.com/security/cve/CVE-2022-0562[CVE-2022-0562] +* link:https://access.redhat.com/security/cve/CVE-2022-0617[CVE-2022-0617] +* link:https://access.redhat.com/security/cve/CVE-2022-0854[CVE-2022-0854] +* link:https://access.redhat.com/security/cve/CVE-2022-0865[CVE-2022-0865] +* link:https://access.redhat.com/security/cve/CVE-2022-0891[CVE-2022-0891] +* link:https://access.redhat.com/security/cve/CVE-2022-0908[CVE-2022-0908] +* link:https://access.redhat.com/security/cve/CVE-2022-0909[CVE-2022-0909] +* link:https://access.redhat.com/security/cve/CVE-2022-0924[CVE-2022-0924] +* link:https://access.redhat.com/security/cve/CVE-2022-1016[CVE-2022-1016] +* link:https://access.redhat.com/security/cve/CVE-2022-1048[CVE-2022-1048] +* link:https://access.redhat.com/security/cve/CVE-2022-1055[CVE-2022-1055] +* link:https://access.redhat.com/security/cve/CVE-2022-1184[CVE-2022-1184] +* link:https://access.redhat.com/security/cve/CVE-2022-1292[CVE-2022-1292] +* link:https://access.redhat.com/security/cve/CVE-2022-1304[CVE-2022-1304] +* link:https://access.redhat.com/security/cve/CVE-2022-1355[CVE-2022-1355] +* link:https://access.redhat.com/security/cve/CVE-2022-1586[CVE-2022-1586] +* link:https://access.redhat.com/security/cve/CVE-2022-1785[CVE-2022-1785] +* link:https://access.redhat.com/security/cve/CVE-2022-1852[CVE-2022-1852] +* link:https://access.redhat.com/security/cve/CVE-2022-1897[CVE-2022-1897] +* link:https://access.redhat.com/security/cve/CVE-2022-1927[CVE-2022-1927] +* link:https://access.redhat.com/security/cve/CVE-2022-2068[CVE-2022-2068] +* link:https://access.redhat.com/security/cve/CVE-2022-2078[CVE-2022-2078] +* link:https://access.redhat.com/security/cve/CVE-2022-2097[CVE-2022-2097] +* link:https://access.redhat.com/security/cve/CVE-2022-2509[CVE-2022-2509] +* link:https://access.redhat.com/security/cve/CVE-2022-2586[CVE-2022-2586] +* link:https://access.redhat.com/security/cve/CVE-2022-2639[CVE-2022-2639] +* link:https://access.redhat.com/security/cve/CVE-2022-2938[CVE-2022-2938] +* link:https://access.redhat.com/security/cve/CVE-2022-3515[CVE-2022-3515] +* link:https://access.redhat.com/security/cve/CVE-2022-20368[CVE-2022-20368] +* link:https://access.redhat.com/security/cve/CVE-2022-21499[CVE-2022-21499] +* link:https://access.redhat.com/security/cve/CVE-2022-21618[CVE-2022-21618] +* link:https://access.redhat.com/security/cve/CVE-2022-21619[CVE-2022-21619] +* link:https://access.redhat.com/security/cve/CVE-2022-21624[CVE-2022-21624] +* link:https://access.redhat.com/security/cve/CVE-2022-21626[CVE-2022-21626] +* link:https://access.redhat.com/security/cve/CVE-2022-21628[CVE-2022-21628] +* link:https://access.redhat.com/security/cve/CVE-2022-22624[CVE-2022-22624] +* link:https://access.redhat.com/security/cve/CVE-2022-22628[CVE-2022-22628] +* link:https://access.redhat.com/security/cve/CVE-2022-22629[CVE-2022-22629] +* link:https://access.redhat.com/security/cve/CVE-2022-22662[CVE-2022-22662] +* link:https://access.redhat.com/security/cve/CVE-2022-22844[CVE-2022-22844] +* link:https://access.redhat.com/security/cve/CVE-2022-23960[CVE-2022-23960] +* link:https://access.redhat.com/security/cve/CVE-2022-24448[CVE-2022-24448] +* link:https://access.redhat.com/security/cve/CVE-2022-25255[CVE-2022-25255] +* link:https://access.redhat.com/security/cve/CVE-2022-26373[CVE-2022-26373] +* link:https://access.redhat.com/security/cve/CVE-2022-26700[CVE-2022-26700] +* link:https://access.redhat.com/security/cve/CVE-2022-26709[CVE-2022-26709] +* link:https://access.redhat.com/security/cve/CVE-2022-26710[CVE-2022-26710] +* link:https://access.redhat.com/security/cve/CVE-2022-26716[CVE-2022-26716] +* link:https://access.redhat.com/security/cve/CVE-2022-26717[CVE-2022-26717] +* link:https://access.redhat.com/security/cve/CVE-2022-26719[CVE-2022-26719] +* link:https://access.redhat.com/security/cve/CVE-2022-27404[CVE-2022-27404] +* link:https://access.redhat.com/security/cve/CVE-2022-27405[CVE-2022-27405] +* link:https://access.redhat.com/security/cve/CVE-2022-27406[CVE-2022-27406] +* link:https://access.redhat.com/security/cve/CVE-2022-27950[CVE-2022-27950] +* link:https://access.redhat.com/security/cve/CVE-2022-28390[CVE-2022-28390] +* link:https://access.redhat.com/security/cve/CVE-2022-28893[CVE-2022-28893] +* link:https://access.redhat.com/security/cve/CVE-2022-29581[CVE-2022-29581] +* link:https://access.redhat.com/security/cve/CVE-2022-30293[CVE-2022-30293] +* link:https://access.redhat.com/security/cve/CVE-2022-34903[CVE-2022-34903] +* link:https://access.redhat.com/security/cve/CVE-2022-36946[CVE-2022-36946] +* link:https://access.redhat.com/security/cve/CVE-2022-37434[CVE-2022-37434] +* link:https://access.redhat.com/security/cve/CVE-2022-39399[CVE-2022-39399]