<p>When releasing a Helm chart, Kubernetes resources have Helm's <code>.Release.Name</code> prepended to their names. In the Chart I'm writing separate namespaces with default resource naming is enough, and the additional prefix is verbose and unwanted. Vault is a dependency of my Chart.</p>
<p>Is there a way I can achieve this using Helm? Ideally, I should only be able to deploy this chart once per namespace, supplying a namespace and release name also feel redundant.</p>
<pre class="lang-bash prettyprint-override"><code># Specify namespace and release name
helm install --create-namespace -n my-namespace my-release hashicorp/vault

# Vault is named &quot;my-release-vault-...&quot; 
kubectl get svc -n my-namespace
NAME                                  TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
my-release-vault                      ClusterIP   10.98.169.234    &lt;none&gt;        8200/TCP,8201/TCP   8s
</code></pre>

<p>I took a quick look at the Chart and I don't think there is the possibility of doing what is requested.</p>
<p>What you can do is modify the templates yourself, adding the override parameter for names/namespaces and try doing a PR against the Hashicorp repo; maybe they didn't think this feature could be useful.</p>
<p>Otherwise, you simply create a custom CHANGELOG where you track all these changes that remind you that you have to make changes to the repository every time you download a new version. It's a maintenance job you won't ignore, but it often happens in Enterprise and highly customized environments that you have to modify the Vendor templates.</p>
<p>This is where the definition of the name happens:
<a href="https://raw.githubusercontent.com/hashicorp/vault-helm/main/templates/_helpers.tpl" rel="nofollow noreferrer">https://raw.githubusercontent.com/hashicorp/vault-helm/main/templates/_helpers.tpl</a>
(First block)</p>
