nfs: upgrade nfs-ganesha to 3.5 version

[kam1kaze]

Signed-off-by: Oleksii Kravchenko kamikaze.ua@gmail.com

Description of your changes:
We start to use NFS rook operator a few weeks ago and were faced with the issue when NFS server was killed by OOM under the heavy load. Adding more memory didn't help. So I checked nfs-ganesha changelog for OOM fixes and found issue related to our problem nfs-ganesha/nfs-ganesha#116. It was merged in the recent version. Upgrade nfs-ganesha to 3.5 version completely resolves high memory consumption.

Which issue is resolved by this Pull Request:
Resolves #

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
• Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
• Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
• Reviewed the developer guide on Submitting a Pull Request
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.
• Pending release notes updated with breaking and/or notable changes, if necessary.
• Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
• Code generation (make codegen) has been run to update object specifications, if necessary.

[travisn]

The commitlint bot is complaining about the commit message. You can change it to:

nfs: bump nfs-ganesha to 3.5 version

Also please add a brief paragraph to the commit message explaining the change.

[thotz]

Since bumpup from 2.7 to 3.5 any nfs-ganesha config changes need to modified ?

[kam1kaze]

@travisn just updated the commit message
@thotz https://github.com/nfs-ganesha/nfs-ganesha/blame/next/src/doc/man/ganesha-export-config.rst I didn't find any changes at least for the last 3 years.
BTW, we are using the updated version in prod for 1 week