-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix: PVCs in state: "Lost" #141
Comments
Consider removing nfs pvcs and doing something like this: |
This could be useful for a longhorn migration: |
I've correlated several timestamps and am now convinced that the issue is with flux. I opened an issue here: In the interim, I'm going to attempt to work around this by adding the uid to all of the PVs. Here is a list generated with PowerShell:
|
All PVCs are now showing as bound. I'll keep this open so that I can:
|
Change the storage class of NFS per the example here:
https://levelup.gitconnected.com/how-to-use-nfs-in-kubernetes-cluster-storage-class-ed1179a83817
Also, do some researching after this explosion occured after importing node1 into terraform and draining the node:
https://stackoverflow.com/questions/51358856/kubernetes-cant-delete-persistentvolumeclaim-pvc
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#storage-object-in-use-protection
The text was updated successfully, but these errors were encountered: