StorageClass reclaimPolicy vs onDelete vs archiveOnDelete

[jinhee6930]

Hi, I have some question.
I understood that reclaimPolicy and onDelete define the same behavior.

▶ onDelete Description
(https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner)
If it exists and has a delete value, delete the directory, if it exists and has a retain value, save the directory.

▶ StorageClass reclaimPolicy Description
(https://kubernetes.io/docs/concepts/storage/storage-classes/#reclaim-policy)
PersistentVolumes that are dynamically created by a StorageClass will have the reclaim policy specified in the reclaimPolicy field of the class, which can be either Delete or Retain.

▶ PV reclaimPolicy Description
(https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaiming)
Retain: The Retain reclaim policy allows for manual reclamation of the resource. When the PersistentVolumeClaim is deleted, the PersistentVolume still exists and the volume is considered "released".
Delete: For volume plugins that support the Delete reclaim policy, deletion removes both the PersistentVolume object from Kubernetes, as well as the associated storage asset in the external infrastructure.

▶ Questions
Q1. Do reclaimPolicy and onDelete mean the same thing?
Q2. What happens if StorageClass's reclaimPolicy=Delete, onDelete=retain, or reclaimPolicy=Retain, onDelete=delete? Is there a priority between reclaimPolicy and onDelete?
Q3. I ran an archiveOnDelete test. When reclaimPolicy=Retain, the archived- directory was not created regardless of whether archiveOnDelete was true or false. Does archiveOnDelete only have meaning when reclaimPolicy=Delete?

If I misunderstood anything, please let me know.
Thank you.