Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: Missing "Skip_Empty_Lines" property in ClusterInput CRD for tail configuration. #1349

Closed
btalakola opened this issue Sep 17, 2024 · 0 comments · Fixed by #1352
Closed
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@btalakola
Copy link
Contributor

btalakola commented Sep 17, 2024

Describe the issue

HI Team,
Hi Team, "Skip_Empty_Lines" property is there if we deploy fluent-bit using fluent-bit helm charts. Below is the reference from fluent bit official manual.
https://docs.fluentbit.io/manual/pipeline/inputs/tail
But the same property is missed out if we deploy fluent-bit using fluent-operator helm charts. "Skip_Empty_Lines" is missed out in ClusterInput CRD as well.
https://github.com/fluent/fluent-operator/blob/master/charts/fluent-operator/charts/fluent-bit-crds/crds/fluentbit.fluent.io_clusterinputs.yaml#L674-L834

Could you please look into this issue?

To Reproduce

Deploy fluent-bit using fluent-operator helm chart. If we verify the ClusterInput CRD, "Skip_Empty_Lines" property is missing for tail configuration.

Expected behavior

End user should be able add the "Skip_Empty_Lines" property to the ClusterInput > Tail configuration.

Your Environment

 Fluent Operator version: v3.1.0
- Container Runtime: containerd
- Operating system: Ubuntu 22.04.4 LTS

How did you install fluent operator?

Deploy fluent-bit using fluent-operator helm chart in k8s environment.

Additional context

No response

@cw-Guo cw-Guo added help wanted Extra attention is needed good first issue Good for newcomers labels Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants