- Newest
- Most votes
- Most comments
I do see that you are using NetApp ONTAP CSI driver (Trident) and you are looking for help in writing a PV yaml file. You might already be aware that, NetApp's Astra Trident provides dynamic storage orchestration using a Container Storage Interface (CSI) compliant driver. This allows Amazon EKS clusters to manage the lifecycle of persistent volumes (PVs) backed by Amazon FSx for NetApp ONTAP file systems.
You can consider checking below NetApp documentation for Use Astra Trident with Amazon FSx for NetApp ONTAP
We have successfully used dynamic provisioning with Trident and FSx volumes. The only issue we have is they all have persistentVolumeReclaimPolicy set to delete on the PVC's which means if the PVC is deleted the volume is deleted too. So this is not good for us. Is there a way to change this so the dynamic volume has persistentVolumeReclaimPolicy set to retain? and how to you reconnect to an existing volume when the dynamic provisioned PVC gets created again?
TIA, Bob
This is my solution:
- create the original PV using dynamic provisioning supplied by the Trident ONTAP CSI driver.
- Immediately edit the PV that was created and change the persistentVolumeReclaimPolicy from Delete to Retain
- If the PVC is ever deleted the PV will remain. Edit it again and remove the claim from the PV. It should then say Available as its Status.
- Recreated the PVC, referencing the old PV volumeName.
- Any new pods should now be able to mount the PVC and allow access to the FSx volume in the pod's file system.
Good luck.
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
What about defining a statically provisioned PV using NetApp ONTAP CSI driver? My FSx volume is already there I just want to be able to mount it via a PVC in my pod. Is this possible?