You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, most of the templates omit .metadata.namespace.
This works fine with helm install / helm upgrade where all the manifests without a namespace will be installed to --namespace anyway.
However, helm template will produce the manifests as-is (with no namespace), regardless of --namespace, forcing users to add the namespace manually, or use additional tools on top like kustomize.
The text was updated successfully, but these errors were encountered:
This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
I'm also annoyed by the same issue. Specially in my case where I have a CDK8S setup with several setupts, having to patch specific files is not convenient at all.
Currently, most of the templates omit
.metadata.namespace
.This works fine with
helm install
/helm upgrade
where all the manifests without a namespace will be installed to--namespace
anyway.However,
helm template
will produce the manifests as-is (with no namespace), regardless of--namespace
, forcing users to add the namespace manually, or use additional tools on top like kustomize.The text was updated successfully, but these errors were encountered: