You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For ease of maintenance and customization, it would be great to have multiple config files, one for each type of kubernetes log. In fact, in my situation, I have to override the parser for audit log (see #519), but still rely on default config for the others.
Would you welcome such refactor?
Moreover, this could be a non-breaking change I guess, because this would be feasible to change the main kubernetes.conf file as an includer of each sub-file. So, if it is replaced, new includes would be omitted.
In a longer sight, this would allow more souple configuration from env. Something like this in kubernetes.conf
include "kubernetes-audit-#{ENV['FLUENT_KUBERNETES_AUDIT_MODE'] ||"legacy"}.conf
The text was updated successfully, but these errors were encountered:
Hi!
For ease of maintenance and customization, it would be great to have multiple config files, one for each type of kubernetes log. In fact, in my situation, I have to override the parser for audit log (see #519), but still rely on default config for the others.
Would you welcome such refactor?
Moreover, this could be a non-breaking change I guess, because this would be feasible to change the main
kubernetes.conf
file as an includer of each sub-file. So, if it is replaced, new includes would be omitted.In a longer sight, this would allow more souple configuration from env. Something like this in
kubernetes.conf
The text was updated successfully, but these errors were encountered: