|
| 1 | +//module included in cluster-logging-release-notes.adoc |
| 2 | +:_content-type: REFERENCE |
| 3 | +[id="cluster-logging-release-notes-5-4-3"] |
| 4 | += Logging 5.4.3 |
| 5 | +This release includes link:https://access.redhat.com/errata/RHBA-2022:5556[RHBA-2022:5556-OpenShift Logging Bug Fix Release 5.4.3]. |
| 6 | + |
| 7 | +[id="openshift-logging-elasticsearch-dep"] |
| 8 | +== Elasticsearch Operator deprecation notice |
| 9 | +In {logging} 5.4.3 the Elasticsearch Operator is deprecated and is planned to be removed in a future release. Red Hat will provide bug fixes and support for this feature during the current release lifecycle, but this feature will no longer receive enhancements and will be removed. As an alternative to using the Elasticsearch Operator to manage the default log storage, you can use the Loki Operator. |
| 10 | + |
| 11 | +[id="openshift-logging-5-4-3-bug-fixes"] |
| 12 | +== Bug fixes |
| 13 | +* Before this update, the OpenShift Logging Dashboard showed the number of active primary shards instead of all active shards. With this update, the dashboard displays all active shards. (link:https://issues.redhat.com//browse/LOG-2781[LOG-2781]) |
| 14 | + |
| 15 | +* Before this update, a bug in a library used by `elasticsearch-operator` contained a denial of service attack vulnerability. With this update, the library has been updated to a version that does not contain this vulnerability. (link:https://issues.redhat.com//browse/LOG-2816[LOG-2816]) |
| 16 | + |
| 17 | +* Before this update, when configuring Vector to forward logs to Loki, it was not possible to set a custom bearer token or use the default token if Loki had TLS enabled. With this update, Vector can forward logs to Loki using tokens with TLS enabled. (link:https://issues.redhat.com//browse/https://issues.redhat.com//browse/LOG-2786[LOG-2786] |
| 18 | + |
| 19 | +* Before this update, the ElasticSearch Operator omitted the `referencePolicy` property of the `ImageStream` custom resource when selecting an `oauth-proxy` image. This omission caused the Kibana deployment to fail in specific environments. With this update, using `referencePolicy` resolves the issue, and the Operator can deploy Kibana successfully. (link:https://issues.redhat.com/browse/LOG-2791[LOG-2791]) |
| 20 | + |
| 21 | +* Before this update, alerting rules for the `ClusterLogForwarder` custom resource did not take multiple forward outputs into account. This update resolves the issue. (link:https://issues.redhat.com/browse/LOG-2640[LOG-2640]) |
| 22 | + |
| 23 | +* Before this update, clusters configured to forward logs to Amazon CloudWatch wrote rejected log files to temporary storage, causing cluster instability over time. With this update, chunk backup for CloudWatch has been disabled, resolving the issue. (link:https://issues.redhat.com/browse/LOG-2768[LOG-2768]) |
| 24 | + |
| 25 | +[id="openshift-logging-5-4-3-CVEs"] |
| 26 | +== CVEs |
| 27 | +.Click to expand CVEs |
| 28 | +[%collapsible] |
| 29 | +==== |
| 30 | +* link:https://access.redhat.com/security/cve/CVE-2020-28915[CVE-2020-28915] |
| 31 | +* link:https://access.redhat.com/security/cve/CVE-2021-40528[CVE-2021-40528] |
| 32 | +* link:https://access.redhat.com/security/cve/CVE-2022-1271[CVE-2022-1271] |
| 33 | +* link:https://access.redhat.com/security/cve/CVE-2022-1621[CVE-2022-1621] |
| 34 | +* link:https://access.redhat.com/security/cve/CVE-2022-1629[CVE-2022-1629] |
| 35 | +* link:https://access.redhat.com/security/cve/CVE-2022-22576[CVE-2022-22576] |
| 36 | +* link:https://access.redhat.com/security/cve/CVE-2022-25313[CVE-2022-25313] |
| 37 | +* link:https://access.redhat.com/security/cve/CVE-2022-25314[CVE-2022-25314] |
| 38 | +* link:https://access.redhat.com/security/cve/CVE-2022-26691[CVE-2022-26691] |
| 39 | +* link:https://access.redhat.com/security/cve/CVE-2022-27666[CVE-2022-27666] |
| 40 | +* link:https://access.redhat.com/security/cve/CVE-2022-27774[CVE-2022-27774] |
| 41 | +* link:https://access.redhat.com/security/cve/CVE-2022-27776[CVE-2022-27776] |
| 42 | +* link:https://access.redhat.com/security/cve/CVE-2022-27782[CVE-2022-27782] |
| 43 | +* link:https://access.redhat.com/security/cve/CVE-2022-29824[CVE-2022-29824] |
| 44 | +==== |
0 commit comments