feat: add namespaceOverride option

[honarkhah]

Summary

Add support for namespaceOverride across all charts that were missing it: fluent-bit, fluent-bit-aggregator, fluent-bit-collector, and fluentd. The fluent-operator chart already had this feature.

This allows deploying chart resources into a namespace different from the Helm release namespace, which is useful for multi-namespace deployments and combined/umbrella charts.

Changes

• _helpers.tpl: Added a <chart>.namespace template helper to each chart that returns .Values.namespaceOverride if set, otherwise falls back to .Release.Namespace.
• values.yaml: Added namespaceOverride value (defaults to empty) to each chart.
• All templates: Replaced hardcoded {{ .Release.Namespace }} references with {{ include "<chart>.namespace" . }} across all resource templates.

Affected Charts

Chart	Files Changed
fluent-bit	17 templates + values.yaml
fluent-bit-aggregator	13 templates + values.yaml
fluent-bit-collector	10 templates + values.yaml
fluentd	4 templates + values.yaml

Usage

# Override the namespace for all chart resources
namespaceOverride: "custom-namespace"

When namespaceOverride is not set, behaviour is unchanged — resources are deployed to the Helm release namespace as before.

Backwards Compatibility

This change is fully backwards compatible. When namespaceOverride is empty or unset, the helper falls back to .Release.Namespace, preserving existing behaviour.

Fixes

• Fluent-bit: add namespace variable #291
• Option to override namespace #103

[stevehipwell]

@honarkhah I don't see an issue tracking a request for this functionality? In the context of Helm (which these official charts are working in), namespaceOverride is an anti-pattern and usually introduced due to tooling limitations. If you'd like to make a case for us to support this pattern please open an issue to discuss your requirements.

[github-actions]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.