Skip to main content
NetApp Knowledge Base

Cleanup of Persistent Volumes in Trident not reflecting on ONTAP

  1. Last updated
  2. Save as PDF
Views:
109
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • Persistent Volumes
  • Kubernetes
  • Trident

Issue

Persistent Volumes are not auto deleting on the storage backend when we perform Persistent Volumes cleanup (deletion) of Trident managed volumes in Kubernetes.

Note: This can also happen with non-ONTAP NAS backends, such as OTNAP SAN, Solidfire, CVO, and other Cloud Storage supproted solutions.

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.

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Reference
    Confidence
    Validated
    Flag
    False
    Governance
    Experience
    KCS Enabled
    Yes
    Visibility
    Public
    Product Categories
    Cloud Volumes ONTAP (CVO)
    Specialty
    Cloud
  2. Tags
    1. 2009522994