<p>Since I added some additonal initContainers to my Airflow helm chart <a href="https://github.com/apache/airflow/tree/main/chart" rel="nofollow noreferrer">(link)</a>, I was trying to set a default <code>initContainerResources</code> to my helm values and deployment yaml:</p>
<ul>
<li>values.yaml</li>
</ul>
<pre><code># Airflow scheduler settings
scheduler:
  
  initContainerResources:
    resources: 
     limits:
      cpu: 200m
      memory: 255Mi
     requests:
      cpu: 100m
      memory: 128Mi

</code></pre>
<ul>
<li>.. and deployment.yaml</li>
</ul>
<pre><code>...
        - name: scheduler-add-init1
          securityContext:
            allowPrivilegeEscalation: False
          resources:
{{ toYaml .Values.scheduler.initContainerResources.resources | indent 12 }}
...

</code></pre>
<p>However, when I try to render the files with helm template, I get:</p>
<blockquote>
<p>Error: values don't meet the specifications of the schema(s) in the
following chart(s): airflow:</p>
<ul>
<li>scheduler: Additional property initContainerResources is not allowed</li>
</ul>
</blockquote>
<p>My goal was to define the init containers resources together but independent from the scheduler container. What´s wrong with my setup?</p>

Bennimi
<p>Turned out I had the schema validation process blocking me from adding additional parameters. Just added the desired key to the schema and it worked:</p>
<p>values.schema.json</p>
<pre><code>                &quot;initContainerResources&quot;: {
                    &quot;description&quot;: &quot;Add default ressources to all init containers of scheduler.&quot;,
                    &quot;type&quot;: &quot;object&quot;,
                    &quot;default&quot;: &quot;See values.yaml&quot;
                },
</code></pre>
