-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PV with reclaim policy can never be claimed again in vclusters #1464
Comments
Hey guys, Any news on that one ? |
Hey @jpuyobro, thanks for opening the issue. I'll look into reproducing this behavior. |
Hey guys, any news on this issue ? |
Hi, sorry for the delayed answer, I have been able to reproduce it on our latest version, I am looking into it |
heiko-braun
changed the title
PV with reclam policy can never be claimed again in vclusters
PV with reclaim policy can never be claimed again in vclusters
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: