Ownership and permission on NFS PV
martin2176 opened this issue · 6 comments
Feature request:
Instead of having 777 and root:root on the NFS PV directory, would be great if there is an option to set uid:gid , permission mode bits and setgid bit on the directory created by the NFS client provisioner. This will improve security posture and effectively utilizing runasuser and runasgroup, supplmental groups in pod security policy for access .
Implementation request:
Support it via annotation to PVC spec. This will allow PVC to be created with different permissions using same storage class.
If this is not possible, support it as a parameter to Storage class.
We are dealing with the exact same issue when trying to install JFrog XRay. It does not like the global permission of 777 on Postgres and other application data directories.
I would love to have a fix for this one.
We may have fixed this problem by only using posix permissions on the NFS share (basically removed the existing windows permission, it had dual permissions set).
We deployed JFrog XRay successfully after this change.
Note: We use Isilon storage for NFS.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.