Make more fluent-bit configurations configurable via the FluentBit resource #452
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kristian-ZH
changed the title
Kristian-ZH
changed the title
Kristian-ZH
force-pushed
the
extract-additional-fluent-bit-configs
branch
from
d45503f
to
476038d
Compare
|
Thanks, @Kristian-ZH for the contribution! @wanjunlei @wenchajun would you help to review? git commit -s --amend
git push -f |
Signed-off-by: Kristian Zhelyazkov <k.zhelyazkov@sap.com> Signed-off-by: Kristian-ZH <k.zhelyazkov@sap.com>
Kristian-ZH
force-pushed
the
extract-additional-fluent-bit-configs
branch
from
476038d
to
b72d491
Compare
wenchajun
approved these changes
Nov 21, 2022
benjaminhuo
approved these changes
Nov 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Adds more configurations in the fluent-bit Daemonset. In this way, FB becomes more extensible and flexible for different scenarios.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduced a user-facing change?