CODEWITHSUNDEEP
kubernetes
Falcon
Falcon

Reputation: 91

PVC behavior with Dynamic Provision and Replicaset

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

Upvotes: 1

Views: 447

Answers (1)

Harsh Manvar
Harsh Manvar

Reputation: 30208

another host mean another Kubernetes node?

If POD gets restarted or terminated and scheduled again on another node in that case if PVC and PV exist disk will be mounted to that specific node and POD again starts running. Yes here, PVC and PV will be the same but still depends on Retain policy.

You can read more about : https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes#deployments_vs_statefulsets

PersistentVolumes can have various reclaim policies, including "Retain", "Recycle", and "Delete". For dynamically provisioned PersistentVolumes, the default reclaim policy is "Delete". This means that a dynamically provisioned volume is automatically deleted when a user deletes the corresponding PersistentVolumeClaim.

read more at : https://kubernetes.io/docs/tasks/administer-cluster/change-pv-reclaim-policy/

if your pod gets terminated or restarted means you are not deleting the PVC in that case PV will be there POD will again get attach to PVC and start running on the respective node.

Upvotes: 3

Related Questions