:eyes: on this would be great; Seems `MULTILINE_PA...
# fluent-operator
t
👀 on this would be great; Seems
MULTILINE_PARSER
does-not take effect even though secrets are as expected. https://github.com/fluent/fluent-operator/issues/1307
Ok it was related to the resource type and my expectation; But raises question why is there no CRD for
inputs
? https://github.com/fluent/fluent-operator/tree/master/charts/fluent-operator/charts/fluent-bit-crds/crds Above issue was caused due to another cluster level Input invalidating it.
ah, you mean namespace-scoped inputs instead of cluster inputs?
t
Hey Pat, yes,
inputs
instead of
clusterinputs
p
Not sure, there seems to be an issue around it that was closed so probably one for @Benjamin Huo: https://github.com/fluent/fluent-operator/issues/521
t
Cheers, meanwhile i will explore avenue without having to create cluster level resource (as now atleast i understand why it was not working in first place).
p
there's always the helm chart as well
t
I think this is bit flawed; i cannot create
input
(i.e namespace) and
MultilineParser
is not recognised as
parser
if you want to use it as
multiline
Filter
So that makes it only possible to use it as
multilineParser
argument with
ClusterInputs
and for that to be used, you need to create
ClusterMultilineParser
with
ClusterInputs
otherwise it wont see namespace
uid
prefix resource. Or i could (is possible 😄) missing something here.
ClusterInput
&
ClusterMultilineParser
is not ideal for non privileged users (or namespace scoped users)
Also another thing noticed; multilineparser is missused and becomes clusterlevel or in other words multilineparser & clusterMultilineParser doesnot make any difference when it comes to secrets & config.