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
With a Vcluster (with persistentVolumes enabled, nodes sync enabled, hoststorageClasses enabled, A volume created with Reclaim policy can never be reclaim. The PV never return to "Available" state.
What did you expect to happen?
We should be able to reclaim this PV inside a vcluster and attach it again.
How can we reproduce it (as minimally and precisely as possible)?
How to reproduce :
In a vCluster Create a PVC with reclaim policy set to retain, a PV is created
Remove the pods using it
Delete the PVC: the PV go to state "Released"
Edit the PV to remove in the spec the "claimRef" part
In a non-vcluster env, the PV goes to state "Available" and can be claimed again
In a vcluster env, the PV stays in the state "Released" and a claimRef is added (it can't be removed). The claim ref is the claim information on "host" cluster
What happened?
With a Vcluster (with persistentVolumes enabled, nodes sync enabled, hoststorageClasses enabled, A volume created with Reclaim policy can never be reclaim. The PV never return to "Available" state.
What did you expect to happen?
We should be able to reclaim this PV inside a vcluster and attach it again.
How can we reproduce it (as minimally and precisely as possible)?
How to reproduce :
In a non-vcluster env, the PV goes to state "Available" and can be claimed again
In a vcluster env, the PV stays in the state "Released" and a claimRef is added (it can't be removed). The claim ref is the claim information on "host" cluster
Anything else we need to know?
No response
Host cluster Kubernetes version
Host cluster Kubernetes distribution
vlcuster version
Vcluster Kubernetes distribution(k3s(default)), k8s, k0s)
v1.28.2+k3s1
OS and Arch
The text was updated successfully, but these errors were encountered: