What would you like to be added:
It would be good if the network operator handles the dependency installation to use NFSoRDMA. For example, the operator has the following option to enable NFSRDMA.
|
| ENABLE_NFSRDMA |N|`"false"`| enable loading of nfs relates storage modules from mofed container| |
However, the nfs-common in Ubuntu with necessary NFS commands and libraries is not installed out of the box so the NFS mount fails if the dependency is not satisfied by hand.
This is one example with Trident but NFSoRDMA is supported with other storage from other vendors so it would be nice if it's handled in the operator in a vendor agnostic way.
https://docs.netapp.com/us-en/trident/trident-use/worker-node-prep.html#nfs-volumes
Why is this needed:
Seamless UX and managed experience by the operator.
What would you like to be added:
It would be good if the network operator handles the dependency installation to use NFSoRDMA. For example, the operator has the following option to enable NFSRDMA.
network-operator/docs/mofed-container-env-vars.md
Line 24 in a528454
However, the
nfs-commonin Ubuntu with necessary NFS commands and libraries is not installed out of the box so the NFS mount fails if the dependency is not satisfied by hand.This is one example with Trident but NFSoRDMA is supported with other storage from other vendors so it would be nice if it's handled in the operator in a vendor agnostic way.
https://docs.netapp.com/us-en/trident/trident-use/worker-node-prep.html#nfs-volumes
Why is this needed:
Seamless UX and managed experience by the operator.