Understanding nfs-provisioner

[Akito]

I’m trying to understand nfs-provisioner as to how it works with persistent storages.
Related to

Understanding PVC, stateful sets and restarted pods

Hello, i’m pretty new at k8s, i’m reading about the persistent volumes and i’m trying to understand how exactly kubernetes manages them when pod is scheduled for a restart? Let’s say i have 5 pods that each one needs to store a state in the PV, and should reload the data when a pod crashes and restarts. How does the scheduler knows to attach the new pod to the old PV? This happens only on stateful sets and not stateless right? (in stateless it will recreate the pod with a fresh volume?) For Stateful sets - when pod is rescheduled, how does it know to attach itself to one of the failed pods? …

What I mainly want to know:

If I use a hostPath is there a risk of automatic deletion of its contents?
What is the best method to make absolutely sure that the volume free for provisioning is under no way deleted?

I need to use nfs-provisioner to store some certificates and I need to make sure that they are never gone, whatever happens to the deployment/cluster/whatever.

[Akito]