Skip to main content
NetApp Knowledge Base

Trident leaves ONTAP snapshot on child PVC after deleting parent PVC and source k8s snapshot

  1. Last updated
  2. Save as PDF
Views:
41
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident
  • ONTAP 9.4 and later
  • NetApp AFF

Issue

Trident leaves snapshot of the child ONTAP volume in the following scenario.
  1. Create a PersistentVolumeClaim (PVC)
  2. Create a Kubernetes volume snapshot for the PVC created in step 1
  3. Create a cloned PVC from the Kubernetes volume snapshot created in step 2
  4. Delete the parent PVC created in step 1
  5. Delete the Kubernetes volume snapshot created at step 2

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.