h4. Description

With the arrival of multi log forwarder in Logging 5.8, configuring a clusterLogging CR and clusterLogForwarder CR called instance is considered "legacy" as explained in the documentation section: "Legacy implementation":

In legacy implementations, you can only use one log forwarder in your cluster. The ClusterLogForwarder resource in this mode must be named instance, and must be created in the openshift-logging namespace. The ClusterLogForwarder resource also requires a corresponding ClusterLogging resource named instance in the openshift-logging namespace.

Then, if this implementation is considered legacy, it should be expected to have detailed how must be configured the new CR Log Forwarder for being able to log forward the logs to the "default" Red Hat Managed Log Storage: Loki or Vector. This means knowing:

• Endpoint to be configured
• Secret to be used and the content
• Token in case that needed
• ClusterRole to be assigned a SA in case that needed to be able to put the logs in the Log Storage
• etc

Having an detailed example in how to do it taking into consideration for Loki the tenants to be configured: infrastructure,application and audit.

Currently, it's not possible to use the multi log forwarder feature to send to the Red Hat Managed Log storage.