Adding Fluentbit's unified networking interface #1217
Merged
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:
This PR adds support for the fluentbit unified networking interface for many output plugins. See the offical docs for more information about the feature https://docs.fluentbit.io/manual/administration/networking
You can use the advanced networking options in most Clusteroutput-Plugins like this:
The operator will then generate the fluentbit-configuration according to the documentation. When running
kubectl get secrets -n fluent fluent-bit-config -o json | jq -r '.data["fluent-bit.conf"]' | base64 -d
we can see that our configuration now includes everything that we defined in the CRD!Which issue(s) this PR fixes:
Fixes #247
Does this PR introduced a user-facing change?
Yes, most CRDs are updated to include the
net
-options and have the corresponding documentation updatedAdditional documentation, usage docs, etc.:
This PR is a 1:1 implementation of the provided documentation at https://docs.fluentbit.io/manual/administration/networking