<p>I'm new to Helm and I haven't quite fully grasped the concepts yet. What I'm currently trying to do is to create a custom chart that basically just sets specific values for another chart that's available in the default stable repository. Pretty much what I want to do is have this:</p>

<pre><code>helm install \
-f my-custom-values.yaml \
stable/target-chart \
--name=my-release
</code></pre>

<p>changed into</p>

<pre><code>helm install my-apps/my-release
</code></pre>

<p>With <code>my-release</code> using the same values in <code>my-custom-values.yaml</code>. It's essentially bundling the pre-existent chart into a new one with my custom values.</p>

<p>Is there a way to do this? I think I might be able to clone the source chart, but I don't feel like that's a practical thing to do.</p>

<p>What is the issue with the first variation? If you have a custom values.yaml that you can pass to helm why do you need to remove it from the command line?</p>

<p>But if you are ready to play around a bit... :)</p>

<p>One way of doing this would be creating your own chart, that will be mainly empty but consist of a requirements.yaml that refers to <code>stable/target-chart</code>.</p>

<p>requirements.yaml (just beside Chart.yaml)</p>

<pre><code>dependencies:
  - name: stable/target-chart
    version: 1.0.0.0.0.0
    alias: somealiasforvaluesyaml
</code></pre>

<p>In your values.yaml you then overwrite the values of that sub-chart:</p>

<pre><code>somealiasforvaluesyaml:
  keyfromthattargetchart: newvalue

  subkeyfromthattargetchart:
    enabled: true
    setting: "value"
</code></pre>

<p>The alias you give in the requirements.yaml is the section in your values.yaml from your chart.</p>

<p>Before installing you need to tell helm to update these requirements:</p>

<pre><code>helm repo update
helm dependency update
</code></pre>

<p>and then just <code>helm install</code> this (virtual?) chart. This chart does not contain any resources to it would not be called a package in linux package managers - but they also use transitional packages or packages that just are a collection of others (like the build-essential)</p>

<p>Considering you already have the values.yaml to overwrite the ones in the target-chart this is all a bit much? Since the cust-values .yaml to pass to install with <code>-f</code> just needs to contain the customization as it will ammend the values.yaml from the target-chart your first command in the question looks like the correct way to go.</p>
