elsnepal

@ksdpmx are you able to look at this? :)

i got stumbled upon this as i was facing simillar issue. We use RBAC in order to isolate namespace access, and when using k9s as mentioned above in original issue...

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...

I think this is bit flawed; I cannot create `inputs` (i.e `namespace`), and `MultilineParser` is not recognized as parser if you want to use it as `multiline` `Filter`. So that...

> @elsnepal , According to the fluentbit documentation, `MultilineParser` can be referred in a filter `parser`. > > > Parser | Specify the parser name to interpret the field. Multiple...

> @elsnepal , According to the fluentbit documentation, `MultilineParser` can be referred in a filter `parser`. > > > Parser | Specify the parser name to interpret the field. Multiple...

Thank you @cw-Guo; those settings were in place, but i doubt CRD's didnt get updated down the line; After doing clean install `combined-multiline` works ``` apiVersion: fluentbit.fluent.io/v1alpha2 kind: ClusterInput metadata:...

Also to make it difficult on parser, ClusterInput being bad is due to those cri exclusion means its not quite matching pattner and you will have to cater for those...

This works as expected, issue was around CRDs update.

This feature would be great for our use-case too, I would like to copy `configmap` from `{{ request.object.metadata.namespace }}` when pre-condition matches to `kube-system`