[enterprise-4.8] Issue in file logging/cluster-logging-external.adoc

[vgri]

Which section(s) is the issue in?

Forwarding logs using the legacy syslog method

What needs fixing?

Following the guide - "You cannot use the config map methods and the Cluster Log Forwarder in the same cluster.".
After creating a ConfigMap from a syslog.conf without a ClusterLogForwarder instance no logs were received in the Syslog.
Confirmed with the OpenShift Logging team, this method is not supported with OpenShift logging operator version 5.x.x.

Please add to the guide that this method is not supported in OpenShift logging operator version 5.x.x.

[cbremble]

Added to Jira: https://issues.redhat.com/browse/RHDEVDOCS-4344

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[cbremble]

/remove-lifecycle rotten

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[cbremble]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[cbremble]

This should be closed based on the outcome of https://issues.redhat.com/browse/RHDEVDOCS-4344.
/close