Skip to main content
NetApp Stage KB

Why are some Trident PVC's  in a Released state?

Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

Trident , OpenShift

Answer

Kubernetes volumes will be one of these phases

 

  • Available -- a free resource that is not yet bound to a claim
  • Bound -- the volume is bound to a claim
  • Released -- the claim has been deleted, but the resource is not yet reclaimed by the cluster
  • Failed -- the volume has failed its automatic reclamation
PVC’s in a “released” state are indicating a deletion of the PVC occurred. A possibility is the PV was deleted outside of Trident. PVC will be in a released state if you deleted the PV before deleting the PVC (the incorrect sequence of events).
 
Another scenario is cloning of PV's (outside of Trident) however a clean up of clones did not occur yet. View the status of all PVC for a given name space with command
kubectl get pv -n trident
 
A PVC in released state will look like the following:
 
NAME                          CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS     CLAIM                             STORAGECLASS   REASON   AGE
pvc-5668bfba-f633-4be6-9239-3ff6bf49431c          1Gi        RWX            Delete           Released   trident/news-repository-pvc     basic                   111d
pvc-9a0682b5-3dd8-46c6-9ded-d7b009801950   100Mi      RWO           Delete           Released   trident/db-volume-otmm-0       basic                   111d
pvc-8a8337ba-627b-4491-b4b3-a37c83dc8a4n      2Gi       RWX            Delete           Released   trident/os-staging-pvc              basic                   111d
 
PVC that are no longer needed should be deleted with command such as     kubectl delete pvc
 
This command will take care of deleting the PV if  the reclaim policy is set to delete for the PVC.
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.
Case Citation
81ed24c6-c4d8-428f-9f85-4ee17dbacc01