<p>I  have a question please, for PVC that is bound to one PV through dynamic storageclass on a pod created by a replica set , if that pod gets terminated and restarted on another host will it get the same PV?
what i saw that the Pod could not be rescheduled till the same PV was active but i am not able to understand what should be the standard behavior and how PVC should react differently between replica set and statefulset</p>

Falcon
<p>another host mean another Kubernetes node?</p>
<p>If POD gets <strong>restarted</strong> or <strong>terminated</strong> and scheduled again on another <strong>node</strong> in that case if PVC and PV exist disk will be mounted to that specific <strong>node</strong> and POD again starts running. Yes here, PVC and PV will be the same but still depends on <strong>Retain</strong> policy.</p>
<p>You can read more about : <a href="https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes#deployments_vs_statefulsets" rel="nofollow noreferrer">https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes#deployments_vs_statefulsets</a></p>
<blockquote>
<p>PersistentVolumes can have various reclaim policies, including
&quot;Retain&quot;, &quot;Recycle&quot;, and &quot;Delete&quot;. For dynamically provisioned
PersistentVolumes, the default reclaim policy is &quot;Delete&quot;. This means
that a dynamically provisioned volume is automatically deleted when a
user deletes the corresponding PersistentVolumeClaim.</p>
</blockquote>
<p>read more at : <a href="https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/</a></p>
<p>if your pod gets terminated or restarted means you are not deleting the <strong>PVC</strong> in that case PV will be there POD will again get attach to <strong>PVC</strong> and start running on the respective node.</p>
