Closed SvenThies closed 3 months ago
Update: The error is not specific to the above config. This also happens when I clone the repo (master) and install the helm chart with
helm install -f charts/fluent-operator/values.yaml fluent-operator charts/fluent-operator
The fluent-bit pod shows:
[2024/06/30 21:24:58] [error] [input:tail:tail.1] parser 'docker' is not registered
i checked the image 3.0.7-debug, i found that parsers.conf
and parsers_multiline.conf
are empty.
# part of the fluent-bit configuration file
fluent-bit.conf: |-
[Service]
Http_Server true
Parsers_File /fluent-bit/config/parsers.conf
Parsers_File /fluent-bit/config/parsers_multiline.conf
# the parser files
root@fluent-bit-fnj2t:/fluent-bit/config# ls
containerd.lua fluent-bit.conf parsers.conf parsers_multiline.conf systemd.lua
root@fluent-bit-fnj2t:/fluent-bit/config# cat parsers.conf
root@fluent-bit-fnj2t:/fluent-bit/config# cat parsers_multiline.conf
root@fluent-bit-fnj2t:/fluent-bit/config#
It's due to https://github.com/fluent/fluent-operator/pull/1138, these two lines were added.
Describe the issue
When deploying fluent-bit with the fluent-operator (plain vanilla with default values) the default parser (cri, json, etc.) are not deployed. As the cri parser is the default parser in the
input: tail
component when selectingkubernetes: true
andcontainerRuntime: containerd
.To Reproduce
Install the chart v2.9.0 with helm (v3.15.2):
using the following
values-test.yaml
:This produces the following error in the fluent-bit container:
Resulting in not correctly parsed logs from kubernetes in the format of containerd log files.
Expected behavior
An additional template that deploys the default parsers using the
clusterparser
CRD. Like so e.g.:Your Environment
How did you install fluent operator?
No response
Additional context
No response