Merge pull request #72505 from shreyasiddhartha/logging-5.8.4-rn-main

DOCS OBSDOCS-847 Logging 5.8.4 Release Notes

Author: Srivaralakshmi

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-4.adoc[leveloffset=+1]
+
 include::modules/logging-release-notes-5-8-3.adoc[leveloffset=+1]
 
 include::modules/logging-release-notes-5-8-2.adoc[leveloffset=+1]

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

@@ -0,0 +1,54 @@
+// module included in /logging/logging-5-8-release-notes
+:_mod-docs-content-type: REFERENCE
+[id="logging-release-notes-5-8-4_{context}"]
+= Logging 5.8.4
+This release includes link:https://access.redhat.com/errata/RHBA-2024:1065[OpenShift Logging Bug Fix Release 5.8.4].
+
+[id="logging-release-notes-5-8-4-bug-fixes"]
+== Bug fixes
+
+* Before this update, the developer console's logs did not account for the current namespace, resulting in query rejection for users without cluster-wide log access. With this update, all supported OCP versions ensure correct namespace inclusion. (link:https://issues.redhat.com/browse/LOG-4905[LOG-4905])
+
+* Before this update, the Cluster Logging Operator deployed `ClusterRoles` supporting LokiStack deployments only when the default log output was  LokiStack. With this update, the roles are split into two groups: read and write. The write roles deploys based on the setting of the default log storage, just like all the roles used to do before. The read roles deploys based on whether the logging console plugin is active. (link:https://issues.redhat.com/browse/LOG-4987[LOG-4987])
+
+* Before this update, multiple `ClusterLogForwarders` defining the same input receiver name had their service endlessly reconciled because of changing `ownerReferences` on one service. With this update, each receiver input will have its own service named with the convention of `<CLF.Name>-<input.Name>`. (link:https://issues.redhat.com/browse/LOG-5009[LOG-5009])
+
+* Before this update, the `ClusterLogForwarder` did not report errors when forwarding logs to cloudwatch without a secret. With this update, the following error message appears when forwarding logs to cloudwatch without a secret: `secret must be provided for cloudwatch output`. (link:https://issues.redhat.com/browse/LOG-5021[LOG-5021])
+
+* Before this update, the `log_forwarder_input_info` included `application`, `infrastructure`, and `audit` input metric points. With this update, `http` is also added as a metric point. (link:https://issues.redhat.com/browse/LOG-5043[LOG-5043])
+
+[id="logging-release-notes-5-8-4-CVEs"]
+== CVEs
+* link:https://access.redhat.com/security/cve/CVE-2021-35937[CVE-2021-35937]
+* link:https://access.redhat.com/security/cve/CVE-2021-35938[CVE-2021-35938]
+* link:https://access.redhat.com/security/cve/CVE-2021-35939[CVE-2021-35939]
+* link:https://access.redhat.com/security/cve/CVE-2022-3545[CVE-2022-3545]
+* link:https://access.redhat.com/security/cve/CVE-2022-24963[CVE-2022-24963]
+* link:https://access.redhat.com/security/cve/CVE-2022-36402[CVE-2022-36402]
+* link:https://access.redhat.com/security/cve/CVE-2022-41858[CVE-2022-41858]
+* link:https://access.redhat.com/security/cve/CVE-2023-2166[CVE-2023-2166]
+* link:https://access.redhat.com/security/cve/CVE-2023-2176[CVE-2023-2176]
+* link:https://access.redhat.com/security/cve/CVE-2023-3777[CVE-2023-3777]
+* link:https://access.redhat.com/security/cve/CVE-2023-3812[CVE-2023-3812]
+* link:https://access.redhat.com/security/cve/CVE-2023-4015[CVE-2023-4015]
+* link:https://access.redhat.com/security/cve/CVE-2023-4622[CVE-2023-4622]
+* link:https://access.redhat.com/security/cve/CVE-2023-4623[CVE-2023-4623]
+* link:https://access.redhat.com/security/cve/CVE-2023-5178[CVE-2023-5178]
+* link:https://access.redhat.com/security/cve/CVE-2023-5363[CVE-2023-5363]
+* link:https://access.redhat.com/security/cve/CVE-2023-5388[CVE-2023-5388]
+* link:https://access.redhat.com/security/cve/CVE-2023-5633[CVE-2023-5633]
+* link:https://access.redhat.com/security/cve/CVE-2023-6679[CVE-2023-6679]
+* link:https://access.redhat.com/security/cve/CVE-2023-7104[CVE-2023-7104]
+* link:https://access.redhat.com/security/cve/CVE-2023-27043[CVE-2023-27043]
+* link:https://access.redhat.com/security/cve/CVE-2023-38409[CVE-2023-38409]
+* link:https://access.redhat.com/security/cve/CVE-2023-40283[CVE-2023-40283]
+* link:https://access.redhat.com/security/cve/CVE-2023-42753[CVE-2023-42753]
+* link:https://access.redhat.com/security/cve/CVE-2023-43804[CVE-2023-43804]
+* link:https://access.redhat.com/security/cve/CVE-2023-45803[CVE-2023-45803]
+* link:https://access.redhat.com/security/cve/CVE-2023-46813[CVE-2023-46813]
+* link:https://access.redhat.com/security/cve/CVE-2024-20918[CVE-2024-20918]
+* link:https://access.redhat.com/security/cve/CVE-2024-20919[CVE-2024-20919]
+* link:https://access.redhat.com/security/cve/CVE-2024-20921[CVE-2024-20921]
+* link:https://access.redhat.com/security/cve/CVE-2024-20926[CVE-2024-20926]
+* link:https://access.redhat.com/security/cve/CVE-2024-20945[CVE-2024-20945]
+* link:https://access.redhat.com/security/cve/CVE-2024-20952[CVE-2024-20952]