Soften gitaly nfs warning
What does this MR do?
As written, the caution regarding gitaly and nfs is quite scary. Are things going to suddenly stop working with GitLab 14.0? The answer is no, and that is clarified in the epic that addresses the tools we are planning to build to enable customers to bulk move projects from existing storage to gitaly cluster. I softened the declaration about nfs support, and added a message about tools to link to the epic.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team