Hide Forgot
Document URL: https://docs.openshift.com/container-platform/3.3/install_config/registry/deploy_registry_existing_clusters.html Section Number and Name: https://docs.openshift.com/container-platform/3.3/install_config/registry/deploy_registry_existing_clusters.html Describe the issue: NFS can not "guarantee" read-after-write consistency, when scaled. We can not recommend this as a good solution for the registry backed volume for production deployments. As NFS as the following known issues, https://docs.openshift.com/container-platform/3.3/install_config/registry/registry_known_issues.html#known-issue-nfs-image-push-fails Suggestions for improvement: Add documentation that states that NFS is not a good solution for the registry backed volume for production deployments. Documentation for production deployments does not scale (we should highlight this). Alternatively production deployments should recommend object based storage for registry that want to scale.
Hi Ryan and Jianwei, I added a note (per Brad's recommendation) to the known issues section. Please take a look at PR3869[1] when you get a chance. Thanks! [1]https://github.com/openshift/openshift-docs/pull/3869
Thank you. Verified that NFS is not recommended for production deployment in our documentation.
Commits pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/1e637aa30d282a3f66324d4be2d4f558841625db Bug 1387712 Added note recommending moving off NFS for production https://github.com/openshift/openshift-docs/commit/f306c3593b3aed10143bdaeeb18f4b1fbe1707f2 Merge pull request #3869 from bmcelvee/BZ1387712 Bug 1387712 Added note recommending moving off NFS for production
Link to document in Customer Portal: https://access.redhat.com/documentation/en-us/openshift_container_platform/3.4/html-single/installation_and_configuration/#known-issue-nfs-image-push-fails