Referencee:https://veducate.co.uk/kubernetes-pvc-terminating/
I still had errors performing deployment, till I released that although I previously was able to delete my PV, my PVC was still in a terminating state. Also realised that I need to be in the right project to see PVC (unless you used --all-namespaces):
[root@okd4-services okd4_files]# oc get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
registry-pv 100Gi RWX Retain Bound openshift-image-registry/image-registry-storage 4h34m
[root@okd4-services ~]# oc get pvc
No resources found in wordpress-test namespace.
[root@okd4-services ~]# oc get pvc --all-namespaces
NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
openshift-image-registry image-registry-storage Terminating registry-pv 100Gi RWX 152d
[root@okd4-services ~]# oc get pvc --all-namespaces^C
[root@okd4-services ~]# kubectl get volumeattachment --all-namespaces
No resources found
[root@okd4-services ~]# oc project
Using project "wordpress-test" on server "https://api.lab.okd.local:6443".
[root@okd4-services ~]# oc project openshift-image-registry
Now using project "openshift-image-registry" on server "https://api.lab.okd.local:6443".
[root@okd4-services ~]# kubectl patch pvc image-registry-storage -p '{"metadata":{"finalizers":null}}'
persistentvolumeclaim/image-registry-storage patched
[root@okd4-services ~]# oc get pvc --all-namespaces
No resources found
[root@okd4-services ~]# oc get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
registry-pv 100Gi RWX Retain Released openshift-image-registry/image-registry-storage 23h
After that I went thru the steps for deleting PV and recreating it.
No comments:
Post a Comment