Can't connect to NFS share with Kubernetes cluster. rpc.statd is not running?

[AeonRemnant]

I'm trying to mount my NFS share on my Talos based Kube cluster using nfs-subdir-external-provisioner and I'm getting the attached error, this indicates rpc.statd is just not enabled.
How exactly would I fix this on TrueNAS Scale?

TrueNAS-SCALE-22.12.2.

I appreciate any help. :)

 

[sretalla]

The answer is in the picture there... use -o nolock in the mount command.

 

[AeonRemnant]

The answer is in the picture there... use -o nolock in the mount command.

I had thought using nolock can cause severe issues when used in a cluster? I mean why would statd not be working anyway?

 

[sretalla]

If you have multiple nodes using the same mount, you're probably not going to want local locking to be the way... but is your workload even doing locking?

Will multiple nodes really be accessing the same paths and touching the same files at the same time?

 

[AeonRemnant]

If you have multiple nodes using the same mount, you're probably not going to want local locking to be the way... but is your workload even doing locking?

Will multiple nodes really be accessing the same paths and touching the same files at the same time?

So my workload is testing scalable game servers using Agones, I'll be using a 32 core machine for this and it'll be running Proxmox with a bunch of Talos installs to handle the load balancing, essentially I'm learning how to make an HA cluster for my upcoming project.

The storage Talos can use easily boils down to Ceph, which I can't deploy due to not having enough nodes or drives, Mayastor which I can't deploy for the same reason, S3 which I don't have practice in, or NFS which I do, and since it's not production, only testing, I figured it was good enough until I work out something more long term.

Still mostly new to this, and I've spun up a functional cluster before, but not for NFS, so I would really like rpc.statd working so I don't run into corruption while developing my game servers.