Open AlistairMcCutcheonIAS opened 4 months ago
It is not possible to change the path in existing volumes.
Rename/move the data folder on the NFS server (if the archiveOnDelete
policy is not set), then delete pv/pvc, then move the data back to its place after creation of new pv/pvc.
In the case of a database, temporary replace the command with ["/bin/sleep", "infinity"]
to maintain data consistency.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Well, since https://github.com/kubernetes/kubernetes/issues/54562 configuration for NFS volumes is effectively set in stone, so there are no easy way to move data automatically.
Nevertheless, I removed the stale label, because this issue can be addressed, at least with mention of some workarounds in the docs.
I've been using this for some time, but I need to change the nfs path that I'm using. I have several persistent volumes which I don't want to delete. As per the readme, the way to install the helm package is:
But is there any way to change the nfs.path after it is installed please?