Thanks for reaching out. Your fix is a simple one, and you can read more details in the Slurm User Guide (https://goo.gle/slurm-gcp-user-guide)
. The "network_storage" field is for the Slurm worker instances, while the "login_network_storage" field is used for the controller and login instances, so that it's possible to isolate the storage available to all workers from the controller and login instances. If you copy and paste the entry you have to the "login_network_storage" field the NFS mount should appear as expected.
You can certainly increase the size and VM type of the controller instance to increase the performance of controller's NFS server, but it will only scale so far in both size and capacity, does not persist through cluster redeployments, and has some other limitations compared to solutions like Filestore that you'll want to make sure you consider.
Let us know how that works and if you have any questions!