There is no way to specify an existing volume name to mount through the openebs' dynamic-nfs-provisioner.
This will be problematic when updating/reprovisioning the cluster because the existing datasets will need to be migrated to the newly generated (empty) datasets, requiring manual operation.
Possible solutions:
[ ] Manually provision an NFS server deployment and specify the PV information so that it's a static PV
[ ] Update dynamic-nfs-provisioner so that it's possible to override the backing PV's name/use an existing PV
[ ] RWO the storage instead of RWX (but then aquisition and media-server will have to be on the same node at all times
Looks like dynamic-nfs-provisioner might be getting deprecated... maybe move to manually spinning up the NFS server (needed anyway for access control...)
alxbl
commented
6 months ago
There is no way to specify an existing volume name to mount through the openebs' dynamic-nfs-provisioner.
This will be problematic when updating/reprovisioning the cluster because the existing datasets will need to be migrated to the newly generated (empty) datasets, requiring manual operation.
Possible solutions:
aquisitionandmedia-serverwill have to be on the same node at all timesLooks like dynamic-nfs-provisioner might be getting deprecated... maybe move to manually spinning up the NFS server (needed anyway for access control...)