Closed amuraru closed 3 years ago
I think you are supposed to specify the namespace via the helm command (--namespace
flag) or if you use templating via kubectl (also --namespace
flag). I omitted the namespace on purpose. See this issue: https://github.com/helm/helm/issues/5465
I am aware of that issue but unfortunately beyond being a best practice it's not working in all CICD tools. We are using for example Spinnaker to drive deployment and neither passing the namespace via command line is not an option or defaulting to current ns is not an option. e.g https://spinnaker.io/guides/user/kubernetes-v2/deploy-helm/#configure-the-bake-manifest-stage Wondering though what are the side-effects and how having the Release.Namespace in impacting helm native installations
I can recall that we had the same discussion with kminion :D
thanks Martin! :)
This is needed in CICD tools where defaulting to namespace is not possible and a namespace is always required.
This is similar to v1 chart version: https://github.com/cloudworkz/kafka-minion-helm-chart/commit/c23f1065e1d02517fce1c0a9994fc4b94e6c84ba