Change nfs path without reinstalling helm package

[AlistairMcCutcheonIAS]

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:

helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner \
    --set nfs.server=x.x.x.x \
    --set nfs.path=/exported/path

But is there any way to change the nfs.path after it is installed please?

[Orhideous]

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Orhideous]

/remove-lifecycle stale

[Orhideous]

Well, since kubernetes/kubernetes#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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale