You can configure your logging subsystem deployment with Custom Resource (CR) YAML files implemented by each Operator.
Red Hat Openshift Logging Operator:
ClusterLogging (CL) - Deploys the collector and forwarder which currently are both implemented by a daemonset running on each node.
ClusterLogForwarder (CLF) - Generates collector configuration to forward logs per user configuration.
OpenShift Elasticsearch Operator:
These CRs are generated and managed by the
ClusterLogging Operator, manual changes cannot be made without being overwritten by the Operator.
ElasticSearch - Configure and deploy an Elasticsearch instance as the default log store.
Kibana - Configure and deploy Kibana instance to search, query and view logs.
Only the configuration options described in this documentation are supported for the logging subsystem.
Do not use any other configuration options, as they are unsupported. Configuration paradigms might change across OpenShift Container Platform releases, and such cases can only be handled gracefully if all configuration possibilities are controlled. If you use configurations other than those described in this documentation, your changes will be overwritten, because Operators are designed to reconcile any differences.
If you must perform configurations not described in the OpenShift Container Platform documentation, you must set your Red Hat OpenShift Logging Operator to
Unmanaged. An unmanaged logging subsystem for Red Hat OpenShift is not supported and does not receive updates until you return its status to