-
Notifications
You must be signed in to change notification settings - Fork 362
Description
What version were you using?
Helm Chart 0.19.16, but bug present in main as well
What environment was the server running in?
Kubernetes 1.32, based on Nats 0.19.16 helm chart
Is this defect reproducible?
This is a small templating error in the nats helm chart.
When deploying using helm chart settings, do not specify .Values.namespaceOverride. the Namespace is not included in the generated manifests, which is causing errors in our argocd + kustomize based deployment, as the the field not defaulted anywhere.
Updating the nats.metadataNamespace to include nats.namespace instead of using it's own resolution logic resolves this issue when evaluated with helm template --dry-run -f values.yaml .
Given the capability you are leveraging, describe your expectation?
I'm expecting the namespace to always be included in the manifets generated by helm so that I do not need to set the namespace override simply to have a working deployment.
Given the expectation, what is the defect you are observing?
The manifests do not include a namespace causing our ArgoCD server to fail to deploy due to the missing field.