<p>let me put you in context. I got pod with a configuration that looks close to this:</p>

<pre><code>spec:
  nodeSets:
  - name: default
    count: 3
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 5Gi
        storageClassName: repd-ssd-xfs
</code></pre>

<p>I also have my <code>StorageClass</code></p>

<pre><code>apiVersion: ...
kind: StorageClass
metadata:
  name: repd-ssd-xfs
parameters:
  type: pd-ssd
  fsType: xfs
  replication-type: regional-pd
  zones: us-central1-a, us-central1-b, us-central1-f
reclaimPolicy: Retain
volumeBindingMode: Immediate
</code></pre>

<p>I delete the namespace of the pod and then apply again and I notice that the pvc that my pod was using change and bound to a new pvc, the last pvc used by the pod is in state released. My question is that Is there any way to specify to the pod to use my old pvc? The <code>StorageClass</code> policy is <code>Retain</code> but that means that I can still using pvc with status released? </p>

YosefMac
<p>In addition to the answer provided by <em>@shashank tyagi</em>. </p>

<p>Have a look at the documentation <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes" rel="nofollow noreferrer">Persistent Volumes</a> and at the section <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#retain" rel="nofollow noreferrer">Retain</a> you can find:</p>

<blockquote>
  <p><strong>When the PersistentVolumeClaim is deleted, the PersistentVolume still
  exists and the volume is considered “released”. But it is not yet
  available for another claim because the previous claimant’s data
  remains on the volume.</strong> An administrator can manually reclaim the
  volume with the following steps.</p>
  
  <ul>
  <li>Delete the PersistentVolume. The associated storage asset in external    infrastructure (such as an AWS EBS, GCE PD, Azure Disk, or
  Cinder    volume) still exists after the PV is deleted.</li>
  <li>Manually clean up the data on the associated storage asset accordingly.</li>
  <li>Manually delete the associated storage asset, or if you want to reuse the same storage asset, create a new PersistentVolume with the<br>
  storage asset definition.</li>
  </ul>
</blockquote>

<p>It could be helpful to check the documentation <a href="https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes" rel="nofollow noreferrer">Persistent volumes with Persistent Disks</a> and this example <a href="https://medium.com/faun/kubernetes-how-to-set-reclaimpolicy-for-persistentvolumeclaim-7eb7d002bb2e" rel="nofollow noreferrer">How to set ReclaimPolicy for PersistentVolumeClaim</a>.</p>

<p><strong>UPDATE</strong> Have a look at the article <a href="https://medium.com/@zhimin.wen/persistent-volume-claim-for-statefulset-8050e396cc51" rel="nofollow noreferrer">Persistent Volume Claim for StatefulSet</a>.</p>
