https://www.cnblogs.com/weifeng1463/p/11490399.html

    1. [rancher@rmaster01 ~]$ kubectl -n rbd-system patch pvc rbd-hub -p '{"metadata":{"finalizers":null}}'
    2. persistentvolumeclaim/rbd-hub patched
    3. [rancher@rmaster01 ~]$ kubectl get pv
    4. NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASONAGE
    5. pvc-9dabb03b-fcdb-4730-8b5d-122210374fda 1Gi RWX Delete Terminating rbd-system/rbd-hub longhorn6h31m
    6. [rancher@rmaster01 ~]$ kubectl patch pv pvc-9dabb03b-fcdb-4730-8b5d-122210374fda -p '{"metadata":{"finalizers":null}}'
    7. persistentvolume/pvc-9dabb03b-fcdb-4730-8b5d-122210374fda patched
    8. [rancher@rmaster01 ~]$ kubectl get pv
    9. No resources found
    10. [rancher@rmaster01 ~]$
    1. [rancher@rmaster01 ~]$ kubectl -n rbd-system get pv
    2. NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
    3. pvc-62201dfc-96d5-4c15-b2cb-088bdf69f6d5 500Gi RWO Retain Terminating 54c2eb3ff2e84304aeee4cb2c2382e97/manual1-gr939832-0 rainbondsssc 157m
    4. [rancher@rmaster01 ~]$ kubectl -n rbd-system patch pv pvc-62201dfc-96d5-4c15-b2cb-088bdf69f6d5 -p '{"metadata":{"finalizers":null}}'
    5. persistentvolume/pvc-62201dfc-96d5-4c15-b2cb-088bdf69f6d5 patched
    6. [rancher@rmaster01 ~]$ kubectl -n rbd-system get pv
    7. No resources found
    8. [rancher@rmaster01 ~]$

    参考信息:
    This happens when persistent volume is protected. You should be able to cross verify this:
    Command:
    kubectl describe pvc PVC_NAME | grep Finalizers
    Output:
    Finalizers: [kubernetes.io/pvc-protection]
    You can fix this by setting finalizers to null using kubectl patch:
    kubectl patch pvc PVC_NAME -p ‘{“metadata”:{“finalizers”: []}}’ —type=merge

    1. [root@test-dev-master01 ~]# kubectl patch pvc test-es01 -p '{"metadata":{"finalizers":null}}' -n xitu-test
    2. persistentvolumeclaim/test-es01 patched