|
| 1 | +// module included in /logging/logging-5-8-release-notes |
| 2 | +:_mod-docs-content-type: REFERENCE |
| 3 | +[id="logging-release-notes-5-8-3_{context}"] |
| 4 | += Logging 5.8.3 |
| 5 | +This release includes link:https://access.redhat.com/errata/RHBA-2024:0693[Logging Bug Fix 5.8.3] and |
| 6 | +link:https://access.redhat.com/errata/RHSA-2024:0728[Logging Security Fix 5.8.3] |
| 7 | + |
| 8 | +[id="logging-release-notes-5-8-3-bug-fixes"] |
| 9 | +== Bug fixes |
| 10 | +* Before this update, when configured to read a custom S3 Certificate Authority the Loki Operator would not automatically update the configuration when the name of the ConfigMap or the contents changed. With this update, the Loki Operator is watching for changes to the ConfigMap and automatically updates the generated configuration. (link:https://issues.redhat.com/browse/LOG-4969[LOG-4969]) |
| 11 | + |
| 12 | +* Before this update, outputs configured without a valid URL caused the collector pods to crash. With this update, outputs are subject to URL validation, resolving the issue. (link:https://issues.redhat.com/browse/LOG-4822[LOG-4822]) |
| 13 | + |
| 14 | +* Before this update the Loki Operator would generate collector configuration fields for outputs that did not specify a secret to utilize the service account bearer token. With this update, an output does not require authentication, resolving the issue. (link:https://issues.redhat.com/browse/LOG-4962[LOG-4962]) |
| 15 | + |
| 16 | +* Before this update, the `tls.insecureSkipVerify` field of an output could not be set to a value of `true` without a secret defined. With this update, a secret is no longer required to set this value. (link:https://issues.redhat.com/browse/LOG-4963[LOG-4963]) |
| 17 | + |
| 18 | +[id="logging-release-notes-5-8-3-CVEs"] |
| 19 | +== CVEs |
| 20 | +* link:https://access.redhat.com/security/cve/CVE-2021-35937[CVE-2021-35937] |
| 21 | +* link:https://access.redhat.com/security/cve/CVE-2021-35938[CVE-2021-35938] |
| 22 | +* link:https://access.redhat.com/security/cve/CVE-2021-35939[CVE-2021-35939] |
| 23 | +* link:https://access.redhat.com/security/cve/CVE-2023-7104[CVE-2023-7104] |
| 24 | +* link:https://access.redhat.com/security/cve/CVE-2023-27043[CVE-2023-27043] |
| 25 | +* link:https://access.redhat.com/security/cve/CVE-2023-48795[CVE-2023-48795] |
| 26 | +* link:https://access.redhat.com/security/cve/CVE-2023-51385[CVE-2023-51385] |
| 27 | +* link:https://access.redhat.com/security/cve/CVE-2024-0553[CVE-2024-0553] |
0 commit comments