Allow for configuring mulitple Logging resources with FluentdConfigs in the same namespace

[joshmeranda]

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

When trying to configure Fleuntd for multiple Logging resources in a logging namespace the user can only configure each within LoggingSpec.fluentd or use the same FluentdConfig for all Logging resources.

The inconsistency between the older .spec.fluentd configuration method and the newer FleuntdConfig method feels un-intuitive.

Describe the solution you'd like

Implement something like FluentBitSpec.loggingRef to allow us to explicitly state which FluentdConfig is intended for which Logging.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[pepov]

Hey @joshmeranda ! Thanks for bringing this up! You are right in that there is no loggingRef in the FluentdConfig resource, but it is for good reason. The purpose of the FluentdConfig resource is to let tenant users manage it themselves (but they must not be able to control which logging resource it belongs). This is described here:
https://github.com/kube-logging/logging-operator/blob/master/docs/standalone-aggregator-config.md

Also you should be able to use different FluentdConfig resources for each Logging resource. Put the FluentdConfig in the controlNamespace of the Logging resource and you should be good to go. Let me know if it doesn't work for you either and I will take a look.