bug: deploying fluent-operator and fluent-bit in different namespaces using "namespaceOverride"

[btalakola]

Describe the issue

HI Team,

I have a requirement to deploy fluent-operator controller and fluent-bit daemonset in differnet namespaces. Found one parameter related to "namespaceOverride". But this is not used to configure the fluent-operator namespace.
https://github.com/fluent/fluent-operator/blob/release-3.2/charts/fluent-operator/values.yaml#L460
When I overrirde this value with fluent-operator namespace value, it didn't work.

fluent-operator deployment is using the release namespace itself.
https://github.com/fluent/fluent-operator/blob/release-3.2/charts/fluent-operator/templates/fluent-operator-deployment.yaml#L6

Also, one more observation, fluent-bit daemonset is created as part of fluent-bit reconciliation logic with the release namespace.
https://github.com/fluent/fluent-operator/blob/release-3.2/controllers/fluentbit_controller.go#L121
Namespace mentioned in fluent-bit custom resources is used for creating this daemonset.
https://github.com/fluent/fluent-operator/blob/release-3.2/pkg/operator/daemonset.go#L34
and this fluent-bit custom resource is also using release namespace.
Can you please guide me how to achieve deploying fluent-operator and fluent-bit daemonset in different namespace?

To Reproduce

Tried deploying fluent-operator and fluent-bit with different namespaces.

Expected behavior

fluent-operator and fluent-bit should be deployed in different namespaces.

Your Environment

- Fluent Operator version: v3.1.0
- Container Runtime: containerd
- Operating system: Ubuntu 22.04.4 LTS

How did you install fluent operator?

Deploy fluent-bit using fluent-operator helm chart.

Additional context

No response

[btalakola]

HI Team, Could you please respond to my requirement? Is it a possible scenario?

[btalakola]

Hi Team,
Able to deploy fluent-bit and fluent-operator in different namespaces by proving the namespace for fluent-operator deployment, serviceAccount, ClusterRoleBinding mapping. There is one more significant change where we need to give the fluent-bit-config namespace in the ClusterFluentBitConfig custom resource.
https://github.com/fluent/fluent-operator/blob/release-3.2/charts/fluent-operator/charts/fluent-bit-crds/crds/fluentbit.fluent.io_clusterfluentbitconfigs.yaml#L191-L231
I have a request here. Can you please make this namespace parameter configurable by adding to ClusterFluentBitConfig customresource > spec section.
https://github.com/fluent/fluent-operator/blob/release-3.2/charts/fluent-operator/templates/fluentbitconfig-fluentBitConfig.yaml#L10