gloomy latch
[what is the default behavior?] as we don't specify this in our storage class. Should we have something here??
if I do not specify the oprion in the SC, what will be the behave? I see randomly provisioning 4.1 and 4.2
what really defines the version if I leave it default (no specified)
round spear
Same as if you don't specify mount options when mounting NFS manually. The client OS (worker node) and and the Server OS (ONTAP) will negotiate what version of NFS to use.
You can specify the nfsvers mount option in either the backend or the storage class to specify which version you wish to use.
gloomy latch
hi @round spear many thanks for the answer but just curios, is not the CSi-driver-NFS play in a role here to define something
or also Kubernetes using the provisioner: csi.trident.netapp.io
slow raven
the default mount options often vary by distribution and Linux kernel version. You can see what mount options Trident uses in your case if you simply mount one of the pods and then run the mount command on the worker node
round spear
Trident only uses the mount options you specify. If you don't specify any options then Trident runs a mount command with no options and the default options for NFS come into play. Like @slow raven mentioned, default mount options vary by OS and version. If you don't want to leave your options to the fate of the NFS daemons, then specify them.
slow raven
usually nfsvers=X,rsize=65536,wsize=65536 or similar should be enough
gloomy latch