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
Describe the bug/feature
The helm compiler uses helm template which allows you to pass through a namespace as a parameter. Unfortunately due to architectural mistakes in helm helm template -n namespace | kubectl apply and helm install -n namespace are not equivalent. helm template does not enforce a namespace, only populates templated namespaces. They don't seem much interesting in fixing it either helm/helm#3553. This causes problems in charts which do not explicitly set namespaces (such as tesoro). Other tools which use helm template internally (argocd for instance) manually enforce a namespace.
To Reproduce
Steps to reproduce the behavior:
Render the tesoro helm chart with kapitan
Check the resource namespaces (spoiler altert: they aren't there)
Expected behavior
Namespaces are set in yaml files.
** If it's a bug (please complete the following information):**
0.30.0-rc.0
Additional context
I am intending to fix this with a secondary external compiler step but it would be nice if kapitan either had an additional parameter to enforce namespace or used the helm_params.namespace value to automatically enforce it.
The text was updated successfully, but these errors were encountered:
Thank you for opening this issue. First of all, please join our #kapitan channel on the kubernetes slack so we can get to chat more about this topic.
I see what you mean, but using the helm input we think it would be wrong to force a behaviour that would not be similar to what helm does on the first place.
What I see possible in the future is to allow for something like a generator to alter the helm chart in a more explicit way, together with making any other changes that are not supported by the helm chart itself.
Describe the bug/feature
The helm compiler uses
helm template
which allows you to pass through a namespace as a parameter. Unfortunately due to architectural mistakes in helmhelm template -n namespace | kubectl apply
andhelm install -n namespace
are not equivalent.helm template
does not enforce a namespace, only populates templated namespaces. They don't seem much interesting in fixing it either helm/helm#3553. This causes problems in charts which do not explicitly set namespaces (such as tesoro). Other tools which use helm template internally (argocd for instance) manually enforce a namespace.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Namespaces are set in yaml files.
** If it's a bug (please complete the following information):**
Additional context
I am intending to fix this with a secondary external compiler step but it would be nice if kapitan either had an additional parameter to enforce namespace or used the helm_params.namespace value to automatically enforce it.
The text was updated successfully, but these errors were encountered: