feat(helm): add namespaceOverride support to FluentBit chart

[hsdp-smulford]

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

When deploying the fluent-operator in a multi-tenant or shared cluster setup, there is no way to deploy FluentBit resources into a namespace other than .Release.Namespace. The namespace field in charts/fluent-operator/templates/fluentbit-fluentBit.yaml is hardcoded to {{ .Release.Namespace }}, forcing FluentBit to always land in the operator's own namespace.

Describe the solution you'd like

Add a fluentbit.namespaceOverride value to charts/fluent-operator/values.yaml that allows users to target a specific namespace for FluentBit resources, falling back to .Release.Namespace when unset.

values.yaml (~line 113):

fluentbit:
  namespaceOverride: ""  # Override the namespace for FluentBit resources; defaults to .Release.Namespace

templates/fluentbit-fluentBit.yaml (line 7):

namespace: {{ default .Release.Namespace .Values.fluentbit.namespaceOverride | quote }}

This follows the namespaceOverride convention already established in charts like kube-prometheus-stack and others in the Helm ecosystem.

Additional context

Relevant files:

• charts/fluent-operator/templates/fluentbit-fluentBit.yaml#L7
• charts/fluent-operator/values.yaml#L113

[marcofranssen]

Great proposal. This would allow users to run the operator in a restricted PSS namespace and run the fluentbit pods in a less restricted namespace.