<p>I have created a basic pod definition in my values.yaml file. However, <code>helm install &lt;name&gt; &lt;path to charts dir&gt;</code> doesn't create the &quot;pod.yaml&quot; in the templates directory. My understanding is that once you define the default values in the &quot;values.yaml&quot;, the templates files gets created. Did I misunderstood? Do I have to add this &quot;pod.yaml&quot; manually?
Here is my pod definition. Thanks!</p>
<pre><code>apiVersion: v1
kind: Pod
metadata:
  name: xxyy
  namespace: default
  labels:
    app: app-name
image:
  repository: imagename
  pullPolicy: IfNotPresent
  repository: &quot;&quot;
  # Overrides the image tag whose default is the chart appVersion.
  tag: &quot;&quot;

replicaCount: 1
imagePullSecrets: []
</code></pre>

Anu
<p><code>helm install</code> <em>reads</em> the files in the <code>templates</code> directory, applies the templating system, and sends the resulting YAML to the Kubernetes cluster; but it never <em>writes</em> a YAML file anywhere.</p>
<p>If you want to see the YAML that your templates would send to the cluster, <a href="https://helm.sh/docs/helm/helm_template/" rel="nofollow noreferrer"><code>helm template</code></a> will print it out.  This is always based on the files that you wrote in the <code>templates</code> directory, though; Helm won't create the YAML on its own.</p>
<p>If you created your chart by running <a href="https://helm.sh/docs/helm/helm_create/" rel="nofollow noreferrer"><code>helm create</code></a> you will get a basic template that contains (among other things) a Deployment spec in <code>templates/deployment.yaml</code>.  You need to edit that file if it doesn't meet your needs.  (Directly working with bare Pods isn't usually what you want: you can't scale them and you generally can't modify them once they're created.)</p>
