Kubernetes Filter as Input processor

[wI2L]

@edsiper Apologies for pinging you directly, but I found this quote from you:

@patrick-stephens I think we can extend the Kubernetes filter and promote to run it as a processor, in that way, we could detect and handle that internally instead of asking the user to configure it.

Actually I would love to simplify that plugin config as much as possible

I read in the documentation that any filter can be used as a processor:
https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/yaml/pipeline-section#running-filters-as-processors

But based on your last comment (not so long ago), I'm unsure if it's possible to use the the kubernetes filter as an input processor (tail in my case).

Of course I could, and will, test it. But I wanted to make sure whether the support was complete, and if other members of the community had success using this filter as a processor ?

[wI2L]

Confirmed from Slack channel that the Kubernetes filters does indeed work as a processor (on the Tail input for example).