<p>I've got a <strong>persistent volume</strong> currently bound to a <strong>deployment</strong>, I've set the <strong>replica count to 0</strong> which I was hoping would unbound the volume - so I could mount it on another pod but it remains in a <code>Bound</code> status.</p>

<p>How can I copy the data from this?  </p>

<p>I'd like to transfer it via scp to another location.</p>

Chris Stryczynski
<blockquote>
  <p>I've got a persistent volume currently bound to a deployment, I've set the replica count to 0 which I was hoping would unbound the volume - so I could mount it on another pod but it remains in a Bound status.</p>
</blockquote>

<p>"Bound" does not mean it is attached to a Node, nor to a Pod (which is pragmatically the same thing); <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#binding" rel="nofollow noreferrer">Bound</a> means that the cloud provider has created a Persistent Volume (out of thin air) in order to fulfill a Persistent Volume Claim for some/all of its allocatable storage. "Bound" relates to its <em>cloud</em> status, not its Pod status. That term exists because kubernetes supports <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaim-policy" rel="nofollow noreferrer">reclaiming</a> volumes, to avoid creating a new cloud storage object if there are existing ones that no one is claiming and fulfill the resource request boundaries.</p>

<p>There's nothing, at least in your question, that prevents you from launching another Pod (in the same Namespace as the Deployment) with a <code>volumes:</code> that points to the <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#claims-as-volumes" rel="nofollow noreferrer"><code>persistentVolumeClaim</code></a> and it will launch that Pod with the volume just as it did in your Deployment. You can then do whatever you'd like in that Pod to egress the data.</p>
