When installing with helm install, the namespace doesn't need to be present on the templates. Helm automatically installs the resources that don't have a specific namespace to the namespace specified in --namespace.
But when using helm template, the resulting templated manifests don't contain a namespace, even though --namespace was used. This is an old issue of Helm (https://github.com/helm/helm/issues/3553). And since a lot of people rely on helm template and then feed that into ArgoCD, it makes to add the namespace field to all namespaced resources.
Thus, this PR adds the namespace in the configmap, deployment, and serviceaccount templates.
Manual test for the chart venafi-kubernetes-agent:
Source: https://venafi.atlassian.net/browse/VC-32006
When installing with
helm install
, the namespace doesn't need to be present on the templates. Helm automatically installs the resources that don't have a specific namespace to the namespace specified in--namespace
.But when using
helm template
, the resulting templated manifests don't contain a namespace, even though--namespace
was used. This is an old issue of Helm (https://github.com/helm/helm/issues/3553). And since a lot of people rely onhelm template
and then feed that into ArgoCD, it makes to add thenamespace
field to all namespaced resources.Thus, this PR adds the
namespace
in the configmap, deployment, and serviceaccount templates.Manual test for the chart
venafi-kubernetes-agent
:Result:
Manual test for the chart
jetstack-agent
:Result: