Support the mountOptions field of StorageClass when nfs-mounting for pods/containers

[scr-oath]

We have a need to create a PVC that mounts NFSv4 with the noac option in order to eliminate any lag between writing on one node and reading (a folder or timestamp, e.g.) on another. Kubernetes StorageClass has a mountOptions field that may be used to pass this option along so that it is used when mounting for use with pods/containers.

The nfs-client-provisioner recently added support for this if you'd like to see how they did it (PR below).

Trident apparently does not support this yet, and we need the feature to continue using our general Trident dynamic provisioner instead of carving up a custom mount point with the incubator (nfs-client-provisioner) solution.

• See https://kubernetes.io/docs/concepts/storage/storage-classes/
• See Propagate StorageClass MountOptions to PVs created by nfs-client-provisioner kubernetes-retired/external-storage#835

[acsulli]

Hello @scr-oath, you can use the k8s mount options, as defined in the storage class, with Trident without issue since 18.01. You can see an example toward the bottom of this blog post.

Andrew

[scr-oath]

Awesome - we must have an older version… sorry for the trouble.