Currently, the MLRun CE Helm chart templates hardcode the namespace as 'mlrun', which restricts installation to only that namespace and impedes use in custom namespaces (e.g., 'controller').
How to fix:
- Search all YAML templates in
charts/mlrun-ce/templates for lines with namespace: mlrun.
- Replace any such instance with
namespace: {{ .Release.Namespace }} to ensure resources are deployed to the namespace specified during Helm installation.
- Confirm all Kubernetes manifests support namespace templating.
- Test chart installation in multiple namespaces to verify correctness.
Impact:
This change will allow MLRun CE to be installed in any namespace, improving compatibility with CI/CD pipelines, multi-tenancy, and cluster organization.
Currently, the MLRun CE Helm chart templates hardcode the namespace as 'mlrun', which restricts installation to only that namespace and impedes use in custom namespaces (e.g., 'controller').
How to fix:
charts/mlrun-ce/templatesfor lines withnamespace: mlrun.namespace: {{ .Release.Namespace }}to ensure resources are deployed to the namespace specified during Helm installation.Impact:
This change will allow MLRun CE to be installed in any namespace, improving compatibility with CI/CD pipelines, multi-tenancy, and cluster organization.