<p>I am having a bit of a problem understanding how the reclaim policy of persistent storage works in detail. I want to define a storage class that saves some logs and if the pods fail or I restart the setup, keeps the data.</p>
<p>According to <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/" rel="nofollow noreferrer">here</a> when I set the <em>reclaim policy</em> to <em>delete</em> the PV and the storage in Azure is removed. If it is set to <em>retain</em> the PV needs to be manually reclaimed.</p>
<p>Now I have the feeling that both types are wrong for my usage (although it seems rather common), as I do want to keep the data (so delete is wrong) and I do not want to manually reclaim the PV every time (so retain seems wrong).</p>
<p>Is there something I misunderstand or is there another way to achieve this?</p>

Manuel 
<p>A reclaim policy of delete won't be deleted when the pod is deleted. This is more about when the PVC itself is deleted what happens with the cloud provider.</p>
<p>Delete means if the PVC itself is deleted the provisioned disk is also removed. If you have a pod which is deleted, as long as future pods use the pvc you'll still have the data, just don't delete the pvc resource also.</p>
<p>Having it set to retain means even when the pv/pvc resource is deleted the provisioned storage will remain just in case</p>
