Feature Request: Allow overriding the namespace for the Grafana Helm chart

[monwolf]

I'd like to request support for overriding the deployment namespace in the Alloy Helm chart, so that subcharts (including Alloy) can be deployed into a different namespace than the parent chart.

Use case
In my environment, I manage multiple infrastructure components using a single umbrella Helm chart. This umbrella chart is deployed into the kube-system namespace, while some of its subcharts need to be deployed into different namespaces depending on configuration passed in values.yaml.

Other subcharts already support this behavior through a configurable namespace value that Helm respects during the rendering phase. With Alloy, however, the namespace is strictly inherited from the parent chart’s release namespace, and cannot be overridden.

Why this matters
Allowing the namespace to be explicitly set in values.yaml would enable more flexible deployments, especially in umbrella-chart scenarios. It would also align Alloy's chart with other ecosystem charts that support namespace overrides for controlled multi-namespace deployments.

Proposed solution
Introduce a value such as:

namespaceOverride: ""

And update the chart templates to use it when defined:

metadata:
  namespace: {{ .Values.namespaceOverride | default .Release.Namespace }}

This would allow users to optionally deploy Alloy into a different namespace without affecting the parent release or requiring separate chart installations.

Additional context
My current setup deploys the umbrella chart into kube-system, but I need Alloy to run in a dedicated namespace (e.g., monitoring). The lack of namespace override makes this impossible using a single umbrella chart.