1. Proposed title of this feature request
Accessible modification of the fluent.conf file in fluentd for customizations
3. What is the nature and description of the request?
We have run into issues where a quick change of the fluent.conf file would have solved an issue or provided an extension quickly. Modifying the conf file requires restarting the container which resets the conf file, meaning that the only way to make these "quick" changes is by mounting an external copy of the fluent.conf file which is a fragile and user-unfriendly solution.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Not that I could find
10. List any affected packages or components.
Fluentd image, EFK stack
@eric, how do these changes relate to our move to configmaps?
Currently we have not tried to implement this with configmaps in Fluentd. During previous discussions we weren't sure if configmaps would be applicable for being able to accomplish this give how the Fluend config is structured.
I think under OSE you could do this in the short term by mounting a secret or configmap at /etc/fluent with fluent.conf in it; as long as the keys secret mounted on top of that, it ought to carry on and that would make it pretty easy to reconfigure.
It's not clear how well this will work in the future with the refactored fluent config that's in origin. We're discussing how best to proceed. Clearly there are going to be customers wanting this type of configuration.
Is this feature needed in 3.3?
This will be available in 3.3 via configmaps.
Documentation is currently being worked on here:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.