You can configure the various features and parameters of the Logging operator using Custom Resource Definitions (CRDs).

You can define outputs (destinations where you want to send your log messages, for example, Elasticsearch, or an Amazon S3 bucket), and flows that use filters and selectors to route log messages to the appropriate outputs. You can also define cluster-wide outputs and flows, for example, to use a centralized output that namespaced users can reference but cannot modify.

You can configure the Logging operator using the following Custom Resource Definitions.

  • logging - The logging resource defines the logging infrastructure for your cluster that collects and transports your log messages. It also contains configurations for Fluentd and Fluent-bit.
  • output - Defines an Output for a logging flow, where the log messages are sent. This is a namespaced resource. See also clusteroutput.
  • flow - Defines a logging flow using filters and outputs. Basically, the flow routes the selected log messages to the specified outputs. This is a namespaced resource. See also clusterflow.
  • clusteroutput - Defines an output that is available from all flows and clusterflows. The operator evaluates clusteroutputs in the controlNamespace only unless allowClusterResourcesFromAllNamespaces is set to true.
  • clusterflow - Defines a logging flow that collects logs from all namespaces by default. The operator evaluates clusterflows in the controlNamespace only unless allowClusterResourcesFromAllNamespaces is set to true.

The following sections show examples on configuring the various components of the Logging operator. For a list of available CRDs, see Custom Resource Definitions.