[Helm/Release] Resources without explicit namespace are created in default namespace

[michael-barker]

When installing a chart that has resources without an explicit namespace set to the release namespace, the resources are created in the default namespace. This can be reproduced by creating a basic chart with helm create.

helm create /tmp/test

new k8s.helm.v3.Release('test', {
      name: 'test',
      chart: 'test',
      version: '0.1.0',
      namespace: 'test',
      repositoryOpts: {
        repo: '/tmp/test',
      },
      values: {
      },
    },
  )

If the following is added to a manifest in the chart then the resource is created in the test namespace as configured in the Release resource above.

metadata:
  namespace: "{{ $.Release.Namespace }}"

[ruckc]

From a helm cli equivalent, the -n {namespace} isn't being provided. This is important for helm cli compatibility, as most charts don't specify the namespace as that should be specified at install time.

[gitfool]

I'm also interested in an option to manipulate the helm chart namespaces. Related to helm/helm#5465 (comment):

After deliberating over the use cases described earlier, I am certain they can be solved in different manners than the proposal described earlier; either by the tooling they're using (flux and spinnaker allow you to specify the namespace), by injecting the metadata yourself through the templates, or by using the post-renderer introduced in Helm 3.1.

TL;DR: chart practices will vary so when namespaces are not configurable via values it would still be useful to be able to override via other mechanisms.