From 04563b36b64cf07e917826fd30705737837f0bda Mon Sep 17 00:00:00 2001
From: "promptless[bot]" <promptless[bot]@users.noreply.github.com>
Date: Tue, 5 May 2026 08:38:14 +0000
Subject: [PATCH] Clarify excess config behavior preserves running aggregator

When multiple FluentdConfig or SyslogNGConfig resources exist in the
same namespace, the documentation now clearly states that:
- The previously-associated config continues to operate normally
- Log forwarding remains uninterrupted while resolving the conflict
- Users should delete the excess config to resolve the issue

Also standardized SyslogNGConfig capitalization.

Related: kube-logging/logging-operator#2232
---
 content/docs/logging-infrastructure/fluentd.md   | 6 +++++-
 content/docs/logging-infrastructure/syslog-ng.md | 6 +++++-
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/content/docs/logging-infrastructure/fluentd.md b/content/docs/logging-infrastructure/fluentd.md
index 933198c8f4..cb3f670abc 100644
--- a/content/docs/logging-infrastructure/fluentd.md
+++ b/content/docs/logging-infrastructure/fluentd.md
@@ -96,7 +96,9 @@ kubectl get fluentdconfig example -o jsonpath='{.status}' | jq .
 }
 ```
 
-If there is a conflict, the controller adds a problem to both resources so that both the operations team and the tenant users can notice the problem. For example, if a `FluentdConfig` is already registered to a `Logging` resource and you create another `FluentdConfig` resource in the same namespace, then the first `FluentdConfig` is left intact, while the second one should have the following status:
+If there is a conflict, the controller adds a problem to both resources so that both the operations team and the tenant users can notice the problem. The previously-associated `FluentdConfig` continues to operate normally, and log forwarding remains uninterrupted while you resolve the excess configuration.
+
+For example, if a `FluentdConfig` is already registered to a `Logging` resource and you create another `FluentdConfig` resource in the same namespace, the first `FluentdConfig` is left intact and its aggregator keeps running, while the second one should have the following status:
 
 ```shell
 kubectl get fluentdconfig example2 -o jsonpath='{.status}' | jq .
@@ -125,6 +127,8 @@ kubectl get logging example -o jsonpath='{.status}' | jq .
 }
 ```
 
+To resolve this conflict, delete the excess `FluentdConfig` resource. The active aggregator will continue running throughout.
+
 ## Custom pvc volume for Fluentd buffers
 
 ```yaml
diff --git a/content/docs/logging-infrastructure/syslog-ng.md b/content/docs/logging-infrastructure/syslog-ng.md
index 80e0ba1099..b61110849c 100644
--- a/content/docs/logging-infrastructure/syslog-ng.md
+++ b/content/docs/logging-infrastructure/syslog-ng.md
@@ -99,7 +99,9 @@ kubectl get syslogngconfig example -o jsonpath='{.status}' | jq .
 }
 ```
 
-If there is a conflict, the controller adds a problem to both resources so that both the operations team and the tenant users can notice the problem. For example, if a `syslogNGConfig` is already registered to a `Logging` resource and you create another `syslogNGConfig` resource in the same namespace, then the first `syslogNGConfig` is left intact, while the second one should have the following status:
+If there is a conflict, the controller adds a problem to both resources so that both the operations team and the tenant users can notice the problem. The previously-associated `SyslogNGConfig` continues to operate normally, and log forwarding remains uninterrupted while you resolve the excess configuration.
+
+For example, if a `SyslogNGConfig` is already registered to a `Logging` resource and you create another `SyslogNGConfig` resource in the same namespace, the first `SyslogNGConfig` is left intact and its aggregator keeps running, while the second one should have the following status:
 
 ```shell
 kubectl get syslogngconfig example2 -o jsonpath='{.status}' | jq .
@@ -128,6 +130,8 @@ kubectl get logging example -o jsonpath='{.status}' | jq .
 }
 ```
 
+To resolve this conflict, delete the excess `SyslogNGConfig` resource. The active aggregator will continue running throughout.
+
 ## Volume mount for buffering
 
 The following example sets a volume mount that syslog-ng can use for buffering messages on the disk (if {{% xref "/docs/configuration/plugins/syslog-ng-outputs/disk_buffer.md" %}} is configured in the output).