[enterprise-4.12] OBSDOCS-1387: Logging Z-Stream Release Notes - 5.8.14

modules/logging-release-notes-5-8-14.adoc

@@ -0,0 +1,41 @@
+// module included in logging-5-8-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="cluster-logging-release-notes-5-8-14_{context}"]
+= Logging 5.8.14
+This release includes link:https://access.redhat.com/errata/RHSA-2024:8317[OpenShift Logging Bug Fix Release 5.8.14] and link:https://access.redhat.com/errata/RHBA-2024:8316[OpenShift Logging Bug Fix Release 5.8.14].
+
+[id="openshift-logging-5-8-14-bug-fixes_{context}"]
+== Bug fixes
+
+* Before this update, it was possible to set the `.containerLimit.maxRecordsPerSecond` parameter in the `ClusterLogForwarder` custom resource to `0`, which could lead to an exception during Vector's startup. With this update, the configuration is validated before being applied, and any invalid values (less than or equal to zero) are rejected. (link:https://issues.redhat.com/browse/LOG-4671[LOG-4671])
+
+* Before this update, the Loki Operator did not automatically add the default `namespace` label to all its alerting rules, which caused Alertmanager instance for user-defined projects to skip routing such alerts. With this update, all alerting and recording rules have the `namespace` label and Alertmanager now routes these alerts correctly. (link:https://issues.redhat.com/browse/LOG-6182[LOG-6182])
+
+* Before this update, the LokiStack ruler component view was not properly initialized, which caused the invalid field error when the ruler component was disabled. With this update, the issue is resolved by the component view being initialized with an empty value. (link:https://issues.redhat.com/browse/LOG-6184[LOG-6184])
+
+[id="openshift-logging-5-8-14-CVEs_{context}"]
+== CVEs
+
+* link:https://access.redhat.com/security/cve/CVE-2023-37920[CVE-2023-37920]
+* link:https://access.redhat.com/security/cve/CVE-2024-2398[CVE-2024-2398]
+* link:https://access.redhat.com/security/cve/CVE-2024-4032[CVE-2024-4032]
+* link:https://access.redhat.com/security/cve/CVE-2024-6232[CVE-2024-6232]
+* link:https://access.redhat.com/security/cve/CVE-2024-6345[CVE-2024-6345]
+* link:https://access.redhat.com/security/cve/CVE-2024-6923[CVE-2024-6923]
+* link:https://access.redhat.com/security/cve/CVE-2024-30203[CVE-2024-30203]
+* link:https://access.redhat.com/security/cve/CVE-2024-30205[CVE-2024-30205]
+* link:https://access.redhat.com/security/cve/CVE-2024-39331[CVE-2024-39331]
+* link:https://access.redhat.com/security/cve/CVE-2024-45490[CVE-2024-45490]
+* link:https://access.redhat.com/security/cve/CVE-2024-45491[CVE-2024-45491]
+* link:https://access.redhat.com/security/cve/CVE-2024-45492[CVE-2024-45492]
+* link:https://access.redhat.com/security/cve/CVE-2024-6119[CVE-2024-6119]
+* link:https://access.redhat.com/security/cve/CVE-2024-24791[CVE-2024-24791]
+* link:https://access.redhat.com/security/cve/CVE-2024-34155[CVE-2024-34155]
+* link:https://access.redhat.com/security/cve/CVE-2024-34156[CVE-2024-34156]
+* link:https://access.redhat.com/security/cve/CVE-2024-34158[CVE-2024-34158]
+* link:https://access.redhat.com/security/cve/CVE-2024-34397[CVE-2024-34397]
+
+[NOTE]
+====
+For detailed information on Red{nbsp}Hat security ratings, review link:https://access.redhat.com/security/updates/classification/#moderate[Severity ratings].
+====

observability/logging/logging_release_notes/logging-5-8-release-notes.adoc

@@ -10,6 +10,8 @@ include::snippets/logging-compatibility-snip.adoc[]
 
 include::snippets/logging-stable-updates-snip.adoc[]
 
+include::modules/logging-release-notes-5-8-14.adoc[leveloffset=+1]
+
 include::modules/logging-release-notes-5-8-13.adoc[leveloffset=+1]
 
 include::modules/logging-release-notes-5-8-12.adoc[leveloffset=+1]