Skip to content

.Release.Namespace not templated into helm chart #1082

Closed

Description

@AlexMichaelJonesNC

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.

Activity

  1. Jarema commented on Dec 8, 2025

    @Jarema
    Member

    Closing, as I think #1083 resolved this.
    If you think otherwise, feel free to reopen.

  2. AlexMichaelJonesNC commented on Jan 12, 2026

    @AlexMichaelJonesNC
    Author

    Should the issue be closed before #1083 is actually merged? I opened this issue to track the issue the PR I opened solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    defectSuspected defect such as a bug or regression

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions