From f2dbf4fe140410663ef41765750b52efbfaeb75e Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Wed, 8 Jan 2020 12:02:52 -0500 Subject: [PATCH] Adding note to logging forward topic on 4.3 changes --- modules/cluster-logging-collector-external.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/modules/cluster-logging-collector-external.adoc b/modules/cluster-logging-collector-external.adoc index dd27b249ed..9791e598a9 100644 --- a/modules/cluster-logging-collector-external.adoc +++ b/modules/cluster-logging-collector-external.adoc @@ -22,6 +22,13 @@ endif::openshift-enterprise[] To configure the *out_forward* plug-in, Create a ConfigMap called `secure-forward` in the `openshift-logging` namespace. On the external aggregator, configure the Fluentd `secure-forward.conf` file. For more information on using the *out_forward* plug-in, see the link:https://docs.fluentd.org/output/forward[Fluentd documentation]. +[IMPORTANT] +==== +Changes introduced by the new log forward feature modified the support for *out_forward* starting with the {product-title} 4.3 release. In {product-title} 4.3, you create a ConfigMap, as described below, to configure out_forward. Any updates to the `secure-forward.conf` section of the Fluentd ConfigMap are removed. You can copy your current `secure-forward.conf` section before upgrading to use when creating the `secure-forward` ConfigMap. + +Additionally, you can add any certificates required by your configuration to a secret named `secure-forward` that will be mounted to the Fluentd pods. +==== + .Sample `secure-forward` configmap [source,yaml] ----