When Valkey is used as a subchart inside an umbrella Helm chart, all resources land in the release namespace. There is no way to redirect them to a dedicated namespace without forking the chart.
Proposed solution:
Add a namespaceOverride value (empty by default — no breaking change) and a helper:
{{- define "valkey.namespace" -}}
{{- default .Release.Namespace .Values.namespaceOverride | trunc 63 | trimSuffix "-" -}}
{{- end -}}
Use {{ include "valkey.namespace" . }} in the namespace: field of all resource metadata. Additionally replace the three .Release.Namespace references used in FQDN construction (init_config.yaml) and namespace selectors (servicemonitor.yaml, podmonitor.yaml).
When Valkey is used as a subchart inside an umbrella Helm chart, all resources land in the release namespace. There is no way to redirect them to a dedicated namespace without forking the chart.
Proposed solution:
Add a namespaceOverride value (empty by default — no breaking change) and a helper:
Use {{ include "valkey.namespace" . }} in the namespace: field of all resource metadata. Additionally replace the three .Release.Namespace references used in FQDN construction (init_config.yaml) and namespace selectors (servicemonitor.yaml, podmonitor.yaml).