<p>The syntax for adding a dependency to a helm 3 chart looks like this (inside of chart.yaml).<br>
How can you specify a release name if you need multiple instances of a dependency?</p>

<pre class="lang-yaml prettyprint-override"><code>apiVersion: v2
name: shared
description: Ingress Controller and Certificate Manager
type: application
version: 0.1.1
appVersion: 0.1.0

dependencies:
  - name: cert-manager
    version: ~0.13
    repository: https://charts.jetstack.io    
</code></pre>

<p>In the CLI it's just <code>helm upgrade -i RELEASE_NAME CHART_NAME -n NAMESPACE</code>
But inside of Chart.yaml the option to specify a release seems to be missing.</p>

<p>The next question I have is if there's a weird way to do it, how would you write the values for each instance in the values.yaml file?</p>

Stephen
<p>After 5 more minutes of searching I found that there's an <code>alias</code> field that can be added, like so:</p>

<pre class="lang-yaml prettyprint-override"><code>dependencies:
  - name: cert-manager
    alias: first-one
    version: ~0.13
    repository: https://charts.jetstack.io
  - name: cert-manager
    alias: second-one
    version: ~0.13
    repository: https://charts.jetstack.io 
</code></pre>

<p>And in the values.yaml file</p>

<pre class="lang-yaml prettyprint-override"><code>first-one:
    # values go here

second-one:
    # values go here
</code></pre>

<p>Reference <a href="https://helm.sh/docs/topics/charts/#the-chartyaml-file" rel="nofollow noreferrer">https://helm.sh/docs/topics/charts/#the-chartyaml-file</a></p>

<p>Using cert-manager is just an example, I can't think of a use-case that would need two instances of that particular chart. I'm hoping to use it for brigade projects</p>
