Specify a custom volume for downloads folder

[dark-vex]

I have introduced the possibility to specify an additional NFS volume for the downloads folder.

This can be useful when using for example the Synology download client and you store the downloaded file on a different volume and/or shared folder.

The best way would be to provide a list of volumes under general.storage.volumes but in order to avoid introducing a breaking changes on the current implementation, I have created a new key general.storage.downloadsVolume

[kubealex]

Hi @dark-vex thank you for your contribution.
May I ask you where the storage resource is introduced? I see the reference in the resources, but I cannot see where the NFS storage is defined in the manifests.

Can you please elaborate a bit?

[dark-vex]

Hey @kubealex sorry I didn't get back to you! It works like the current implementation of cluster external NFS server so the pods will have the nfs server defined under volumes section:

  volumes:
  - name: download-volume
    nfs:
      server: nfs-server.domain.tld
      path: /my-nfs-volume
      readOnly: true

Hope this makes sense

[KnightDoom]

This looks great.
I had to do this manually via a script and patching my k3s deployments.
Will need to ensure sabnzbd is also included. I can contribute once the pull is completed.

Wondering if there is a difference between passing it as a PVC and opening multiple NFS clients in this approach.

[dark-vex]

Wondering if there is a difference between passing it as a PVC and opening multiple NFS clients in this approach.

Performance wise probably yes but I didn't had the chance to perform any test on this matter