Is your feature request related to a problem? Please describe.
At the moment, using a custom Fluent Bit plugin requires building a .so shared library and registering it via the -e flag or in the plugins section of the configuration. The main challenge is that there is no convenient way to supply the .so file to Fluent Bit at runtime. The common workaround today is to build a custom Docker image that includes the shared library, and then use an init container with additional logic to copy the .so file into the required location. This approach is cumbersome and adds unnecessary operational complexity.
Describe the solution you'd like
A better solution IMO would be to extend the Fluent Bit CRD to natively support this use case. For example, the CRD could accept a container image reference and a file path for the .so plugin. The operator would then handle retrieving the plugin from the image and mounting it in the correct location automatically. This would eliminate the need for custom init containers and significantly simplify plugin management.
Additional context
P.S. If you like the idea, I would be happy to create a PR.
Is your feature request related to a problem? Please describe.
At the moment, using a custom Fluent Bit plugin requires building a
.soshared library and registering it via the-eflag or in the plugins section of the configuration. The main challenge is that there is no convenient way to supply the.sofile to Fluent Bit at runtime. The common workaround today is to build a custom Docker image that includes the shared library, and then use an init container with additional logic to copy the.sofile into the required location. This approach is cumbersome and adds unnecessary operational complexity.Describe the solution you'd like
A better solution IMO would be to extend the Fluent Bit CRD to natively support this use case. For example, the CRD could accept a container image reference and a file path for the
.soplugin. The operator would then handle retrieving the plugin from the image and mounting it in the correct location automatically. This would eliminate the need for custom init containers and significantly simplify plugin management.Additional context
P.S. If you like the idea, I would be happy to create a PR.