<p>I have a pod in which I'm running a image.
The pod is not mine but belongs to the company I work for.
Each time I mount a new image in the pod it has access to some predefined &quot;Permanent&quot; folders.</p>
<p>When I use the edit deployment command I see this:</p>
<pre><code> volumeMounts:
        - mountPath: /Data/logs
          name: ba-server-api-dh-pvc
          subPath: logs
        - mountPath: /Data/ErrorAndAbortedBlobs
          name: ba-server-api-dh-pvc
          subPath: ErrorAndAbortedBlobs
        - mountPath: /Data/SuccessfullyTransferredBlobs
          name: ba-server-api-dh-pvc
          subPath: SuccessfullyTransferredBlobs
        - mountPath: /Data/BlobsToBeTransferred
          name: ba-server-api-dh-pvc
          subPath: BlobsToBeTransferred 
</code></pre>
<p>Now I want to manually add another such mountPath so I get another folder in the pod. But when I add it to the deployment config (the one above) and try saving it I get the following error.</p>
<pre><code>&quot;error: deployments.extensions &quot;ba-server-api-dh-deployment&quot; is invalid&quot;
</code></pre>
<p>What can I do to add another permanent folder to the POD?</p>
<p>kind regards</p>

Mr.Gomer
<p>It looks like you haven't specified the volume.</p>
<p>Something looks like this.</p>
<pre><code>...
        volumeMounts:
          - mountPath: /Data/BlobsToBeTransferred
            name: ba-server-api-dh-pvc
            subPath: BlobsToBeTransferred
...
   volume:
     - name: ba-server-api-dh-pvc
       persistentVolumeClaim:
         claimName: ba-server-api-dh-pvc
</code></pre>
<p>Note that you already have a PersistentVolumeClaim named ba-server-api-dh-pvc, otherwise you will have to create.</p>
