liveBook · Manning

ClusterFluentBitConfig

As explained in Logs and Telemetry

ClusterFluentBitConfig is a Fluent Operator custom resource for selecting cluster-wide Fluent Bit input, output, and filter configurations.

ClusterFluentBitConfig is a Fluent Operator custom resource that assembles cluster-wide Fluent Bit inputs, filters, and outputs through selectable plugin configurations. It can target specific namespaces and keep configuration values, including credentials, in Kubernetes secrets. section 4.8

Use the resource to coordinate these configuration areas:

  • Select Input, Filter, and Output resources with label-based match expressions. section 4.8
  • Control log-ingestion behavior such as buffer limits and handling of overlong lines. section 4.8
  • Route matching records to an output such as Elasticsearch using tags like kube.*. section 4.8
Listing 4.10 Helm chart config: fluentbit_v1alpha2_fluentbitconfig.yaml
apiVersion: fluentbit.fluent.io/v1alpha2
kind: FluentBitConfig
metadata:
  name: fluentbitconfig-sample
spec:
  service:                         #1
    flush: 1
    daemon: false
    logLevel: info
    parsersFile: parsers.conf
  inputSelector:       #2
    matchExpressions:        #3
      - key: fluentbit.fluent.io/enabled
        operator: In
        values: ["true"]      #4
  filterSelector:           #5
    matchExpressions:       
      - key: fluentbit.fluent.io/enabled
        operator: In
        values: ["true"]
  outputSelector:
    matchExpressions:
      - key: fluentbit.fluent.io/enabled
        operator: In
        values: ["true"]

Inspect the selector structure used by the analogous FluentBitConfig resource: enabled labels select the input, filter, and output components that form the generated Fluent Bit configuration. section 4.8

How Logs and Telemetry covers it

How deep it goes
Explains selectors, namespace targeting, secrets, and performance controls, but does not detail the operator reconciliation internals.
Examples
Demonstrates enabled-label selectors, container-log tailing, memory limits, skipped long lines, and Elasticsearch output matching kube.*.
What it assumes
Uses Kubernetes resource management and Fluent Bit concepts such as inputs, filters, outputs, tags, and selectors.
What you can do after
Operate cluster-wide Fluent Bit routing by selecting labeled plugin resources and constraining input resource use.
How it connects
Connects Fluent Operator with FluentBit, FluentBitConfig, Input, Output, Filter, Parser, Kubernetes, and Helm.
Cover of Logs and Telemetry
liveBookmanning.com
Read Logs and Telemetry on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Logs and Telemetry. The section links point to the parts of the book it draws on.