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
{{ message }}
This repository has been archived by the owner on Aug 25, 2021. It is now read-only.
Ran into this today when using helm template to generate YAML to be subsequently applied with kubectl.
Today only connect-inject-serviceaccount.yaml and sync-catalog-service-account.yaml appear to be setting metadata.namespace via {{ .Release.Namespace }}
Ideally, helm would do this automatically when running template --namespace=<x> to mirror the behavior of helm install --namespace=<x>, but it does not. See: helm/helm#3553 for a longer discussion.
Other projects, such as Istio, have worked around this limitation by including metadata.name on all resource templates. See: istio/istio#4606
The text was updated successfully, but these errors were encountered:
Ran into this today when using
helm template
to generate YAML to be subsequently applied withkubectl
.Today only
connect-inject-serviceaccount.yaml
andsync-catalog-service-account.yaml
appear to be settingmetadata.namespace
via{{ .Release.Namespace }}
Ideally,
helm
would do this automatically when runningtemplate --namespace=<x>
to mirror the behavior ofhelm install --namespace=<x>
, but it does not. See: helm/helm#3553 for a longer discussion.Other projects, such as Istio, have worked around this limitation by including
metadata.name
on all resource templates. See: istio/istio#4606The text was updated successfully, but these errors were encountered: