How is the skip recovery queue for ONTAP volume applied when Trident deletes PVC?
Applies to
- Trident 26.02 or later
- ONTAP 9
Answer
The skip recovery queue feature for ONTAP volume will be applied when Trident deletes PVC in either of the following cases:
- The PVC has an annotation
trident.netapp.io/skipRecoveryQueue: "true" - The backend's volume provisioning options include
skipRecoveryQueue: "true"
Note:
- If the PVC has an annotation
trident.netapp.io/skipRecoveryQueue: "false", the skip recovery queue feature will not be applied even if the backend's volume provisioning options includeskipRecoveryQueue: "true". - skipRecoveryQueue annotation on PVC: Trident currently does not support applying the skipRecoveryQueue annotation to a PVC after it has already been created. The annotation must be included in the PVC YAML at the time of initial creation.
- skipRecoveryQueue on the backend configuration: The parameter must be nested under the "defaults" section in the backend JSON, and the value "true" must be passed as a string (not a boolean).
Additional Information
- Trident release notes mentions the enhancement "Added support to allow ONTAP volumes to skip recovery queue on deletion" in Trident 25.02.
- Backend configuration options for provisioning volumes (ONTAP SAN driver)
- Backend configuration options for provisioning volumes (ONTAP NAS driver)
- Trident cloned PVCs are sent to the volume recovery queue when deleted
