You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After having used a volume before or created a storage class with a typo in the name, I'd like to remove the volumes from the list of available ones. I've failed doing so, it keeps being listed. Here's what I've tried:
Unmount the volume on the node.
Remove the volume directory on the node (as specified in the storageClassMap part of the ConfigMap; hostDir & mountDir do not exist any longer).
Remove the whole storageClassMap entry in the ConfigMap.
Remove the whole StorageClass object.
Restart all pods in the daemonset for the provisioner.
Still lists my PVs as available with the age of the original creation time and a non-existing storageClass:
$ kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
local-pv-21cd33fd 10015Mi RWO Delete Available my-sc-class-with-typo 52m
$ kubectl get sc/my-sc-class-with-typo
Error from server (NotFound): storageclasses.storage.k8s.io "my-sc-class-with-typo" not found
Is this intentional? I don't want a claim to be taken to those non-existing volumes.
hi, PVs cannot be updated after creation. You must delete PV objects. You don't need to unmount volumes. If you want to fix the storage class name, you can follow the steps below:
After having used a volume before or created a storage class with a typo in the name, I'd like to remove the volumes from the list of available ones. I've failed doing so, it keeps being listed. Here's what I've tried:
storageClassMap
part of the ConfigMap; hostDir & mountDir do not exist any longer).Still lists my PVs as available with the age of the original creation time and a non-existing storageClass:
Is this intentional? I don't want a claim to be taken to those non-existing volumes.
I'm using 2.3.2 on Kubernetes 1.15.0.
(perhaps related: #6)
The text was updated successfully, but these errors were encountered: