<p>Helm is failing when upgrading a chart that contains a new sub-chart</p>

<p>e.g.:</p>

<pre><code>chart
    /templates
    /charts
        /sub-1
    values.yaml
</code></pre>

<p>Now this chart get's updated, and a new sub-chart is added, which contains a configmap etc..</p>

<pre><code>chart
    /templates
    /charts
        /sub-1
        /sub-2
            /templates
                configmap.yaml #config
    values.yaml
</code></pre>

<p>When we run <code>helm upgrade &lt;release&gt; &lt;chart&gt; --install</code> we keep getting:</p>

<p><code>Error: UPGRADE FAILED: no ConfigMap with the name "config" found</code></p>

<p>My guess is that helms tries to diff it with the 'previous' version of <code>config</code> but it does not yet exist. And thus the error. However, how could I make this work without deleting and re-installing the chart. This is not optimal for production scerarios.</p>

RVandersteen
<p>I would just create a blank ConfigMap in whichever Kubernetes namespace you are installing your Chart.</p>

<pre><code>$ kubectl -n &lt;namespace&gt; create cm config
</code></pre>

<p>If for reason it complains about the <code>data</code> field or another field not being available you can always create a dummy one:</p>

<pre><code>$ kubectl -n &lt;namespace&gt; edit cm config
</code></pre>

<p>or</p>

<pre><code>$ kubectl -n &lt;namespace&gt; patch cm config -p '{"data": {"dummy": "dummy1"}}'
</code></pre>
