I’ve been wrestling with this issue myself recently.

There can be both performance and other issues with a db whose data files are on nfs. That said I’ve done this for years without any real problem. Np db corruption so far - but it’s a possibility and I’ve probably been lucky. I have good backups just in case.

Like you I also don’t want to maintain a “pet” database on my file server. I want to spin up databases in kubernetes pods and not use local now storage.

I’ve been investigating using iSCSI instead. It’s “block level” rather than “file level” and performs better with a database. Also none of the locking issues mentioned. It’s a recommended way to do remote storage for a db.

The downside is that it’s less resilient to the file server becoming unavailable.

Might be worth investigating for you as well - I’ll be performing some poc tests to figure out how much of a pain it may be (I don’t want to need to fsck a bunch of targets after a file server reboot).