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

"extraFiles" declared in the values.yaml are not included in the base fluent-bit.conf and custom parser files cannot be imported #2

Open
ghost opened this issue Jan 31, 2024 · 1 comment

Comments

@ghost
Copy link

ghost commented Jan 31, 2024

Currently if you add a conf file to the config.extraFiles field in values.yaml, the file is correctly created and added to the fluentbit container, however, no @INCLUDE statement is dynamically added to the fluent-bit.conf to allow the config data to actually be seen and used. If you want it to be used you have to override the config.service value manually.

Additionally, there isn't a way to add custom parsers as a parser file. You can only define them directly in the config.customParsers field. Just like the extraFiles field, we should add a parserFiles field to allow the submission of additional parsers files. This will allow the dynamic addition of additional parsers following a similar and consistent format to conf files. This will require the creation of the parserFiles field as well as ensuring that those files then get proper references in the fluent-bit.conf file.

@ghost
Copy link
Author

ghost commented Mar 2, 2024

bb8-bot commented:

@justin.vandiver this issue has been inactive for 30 days and is being labelled as ~stale. If this issue is still required please take action by removing the ~stale label and commenting with an update, status, or justification. If this issue is not required please close it or label it as ~delete-me. If no action is taken this issue will be auto closed in 60 days.

@ghost ghost added the stale label Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

0 participants