Hey, I'm currently trying to integrate the fluent-...
# fluent-operator
t
Hey, I'm currently trying to integrate the fluent-operator in multi tenant environment, a PR is upcoming for 2 minor fixes. But there is a more general question about the operator design. Personally I'd like to implement a validating webhook to deal with breaking configuration. IMHO this is actually impossible to do so, as the configuration is set up incrementally. For example once you apply a
Filter
containing new
Parser
definition, it depends on the apply order to make it work. An option could be to have an actual non-dynamic FluentBitConfig or lets call it
Flow
referencing all the filters, parsers, outputs directly so that you can make sure the change is atomic and consistent. An alternative would be copy the dry-run status of all related
FluentBitConfig
and the
ClusterFluentBitConfig
.
To get it right, I don't want to drop all the individual crds like filter and parser. This is also quite nice. Logging operator had similar difficulties and handled it like proposed having a separate flow resource. https://axoflow.com/multi-tenancy-using-logging-operator/ I prefer to use the fluent-operator in order to get use fluent-bit directly, that's why i'm asking and not using logging operator at all.