Custom plugin to make use of secret for sensitive data

[adiforluls]

Is your feature request related to a problem? Please describe.

In case of custom plugins, we simply write the absolute config supplied by the user to fluentbit/fluentd config secret. In case I need to wrap sensitive data (user credentials, auth token etc) in a secret, I cannot do that with custom plugins. The ability to use untyped custom plugins is a fantastic feature that makes fluent-operator flexible and we should think about tying up this loose end.

Describe the solution you'd like

Since this is a generic interface for all plugins, one solution would be to let the user specify the field name and secretKeyRef that holds the value for this key under the customPlugin field in the CRD.

Additional context

Open to suggestions and discussions around this.

[joshuabaird]

This issue is being closed due to inactivity. Please re-open if it is still relevant.