Changing provisioned volume mode to 0777 by adding a chmod call after the dir is created
This is to allow non-root consumer pod to gain access to the volume. It is quite common now that pods are running as non-root user (sometimes even with restricted SCC). The consumer pod should be responsible for preparing the volume (i.e. changing the permission to proper values)
I also added on replace clause in go.mod otherwise it won't build (see #39).
I've tested this change using a dev build running on Openshift 4.8 with portworx backing the server. With this change non-root pods are able to mount provisioned volume and gain access.
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.
Description of your changes:
Changing provisioned volume mode to 0777 by adding a chmod call after the dir is created
This is to allow non-root consumer pod to gain access to the volume. It is quite common now that pods are running as non-root user (sometimes even with restricted SCC). The consumer pod should be responsible for preparing the volume (i.e. changing the permission to proper values)
I also added on replace clause in go.mod otherwise it won't build (see #39).
Which issue is resolved by this Pull Request: Resolves https://github.com/rook/nfs/issues/22 and potentially a band-aid fix for https://github.com/rook/nfs/issues/39
I've tested this change using a dev build running on Openshift 4.8 with portworx backing the server. With this change non-root pods are able to mount provisioned volume and gain access.
Checklist:
make codegen) has been run to update object specifications, if necessary.