From 4fe0643ca98cabfb921afe227fcc6a310caa7fcd Mon Sep 17 00:00:00 2001 From: jmagak Date: Thu, 13 Feb 2025 11:56:56 +0100 Subject: [PATCH] Logging 6.1.2 Release Notes --- modules/log6x-6-1-2-rn.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/log6x-6-1-2-rn.adoc b/modules/log6x-6-1-2-rn.adoc index 26606926fe..5edeb9dbf9 100644 --- a/modules/log6x-6-1-2-rn.adoc +++ b/modules/log6x-6-1-2-rn.adoc @@ -20,13 +20,13 @@ This release includes link:https://access.redhat.com/errata/RHBA-2025:1229[{logg * Before this update, the collector alerting rules contained summary and message fields. With this update, the collector alerting rules contain summary and description fields. (link:https://issues.redhat.com/browse/LOG-6126[LOG-6126]) -* Before this update, the collector metrics dashboard could get removed after an operator upgrade due to a race condition during the transition from the old to the new pod deployment. With this update, labels are added to the dashboard `ConfigMap` to identify the upgraded deployment as the current owner so that it will not be removed. +* Before this update, the collector metrics dashboard could get removed after an Operator upgrade due to a race condition during the transition from the old to the new pod deployment. With this update, labels are added to the dashboard `ConfigMap` to identify the upgraded deployment as the current owner so that it will not be removed. (link:https://issues.redhat.com/browse/LOG-6280[LOG-6280]) * Before this update, when you included infrastructure namespaces in application inputs, their `log_type` would be set to `application`. With this update, the `log_type` of infrastructure namespaces included in application inputs is set to `infrastructure`. (link:https://issues.redhat.com/browse/LOG-6373[LOG-6373]) -* Before this update, the Cluster Logging Operator used a cached client to fetch the `SecurityContextConstraint` cluster resource, which could result in an error when the cache is invalid. With this update, the operator now always retrieves data from the API server instead of using a cache. +* Before this update, the Cluster Logging Operator used a cached client to fetch the `SecurityContextConstraint` cluster resource, which could result in an error when the cache is invalid. With this update, the Operator now always retrieves data from the API server instead of using a cache. (link:https://issues.redhat.com/browse/LOG-6418[LOG-6418]) * Before this update, the logging `must-gather` did not collect resources such as `UIPlugin`, `ClusterLogForwarder`, `LogFileMetricExporter`, and `LokiStack`. With this update, the `must-gather` now collects all of these resources and places them in their respective namespace directory instead of the `cluster-logging` directory.