kubesphere
Storage classes that should not support deleting existing storage volumes
Describe the Bug
1、Storage class test exists, and there is already mounted pvc ‘volume’
2、Delete the storage class test, click on the volume to report an error，some functions of the storage volume cannot be used
Versions Used KubeSphere: v3.3.0
Expected behavior When deleting a storage class, it prompts that there is a storage volume, you need to delete the storage volume first
/assign @f10atin9
Usually we do not remove storageClass when pvc is present, it would lead to some unexpected errors. Do we need to add a confirm operation or disable the delete operation in this case? @VioZhang @stoneshi-yunify
k8s does allow to delete a sc when some volumes provisioned with it, and ks-console follows this rule.
it might be great to add a confirm dialog when there are some volumes exist. When user confirms, the sc can still be deleted.
k8s does allow to delete a sc when some volumes provisioned with it, and ks-console follows this rule.
it might be great to add a confirm dialog when there are some volumes exist. When user confirms, the sc can still be deleted.
I agree with it.