Missing namespace on Helm manifests cause issues with Kustomize

Many Helm resources do not specify the namespace, which can cause issues with Kustomize in some deployments. I have to add it at the "top" level, which automatically applies the desired namespace to all Kustomize resources. Unfortunately, I have a few resources that have to be applied to a different namespace, which this breaks.

I have highlighted the issue in my Nextcloud deployment manifests: : https://github.com/kenlasko/k8s/blob/main/manifests/apps/nextcloud/base/kustomization.yaml

I should be able to define the namespace at the Helm chart level and it should apply the namespace to all namespaced resources.

I recommend that:

namespace: {{ .Release.namespace }}

be added to all namespaced resources, such as:

• deployment
• secret
• service
• serviceAccount

I'd offer to do this myself, but I'm not a developer and not familiar with the process to do such things.

EDIT: Think I managed to submit a pull request to fix this for all objects. Crossing fingers!

Start by reviewing the chart's Helm templates for the namespaced resources listed in the issue, then compare their rendered output with the linked Nextcloud kustomization.yaml. Done means namespaced resources receive the Helm release namespace so Kustomize can preserve different namespaces where needed, while the chart's other objects remain correct.