-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow specify new folder permission. #357
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
@leptonyu Thank you for raising this issue. The issue have less description. Which is not easy to understand in one go, |
From my investigation i come to know that you may be talking about nfs-subdir-external-provisioner/cmd/nfs-subdir-external-provisioner having provisioner.go file . |
Yes, this one. Line 115 nfs-subdir-external-provisioner/cmd/nfs-subdir-external-provisioner/provisioner.go Line 115 in 59a3ca2
|
I think, Hardcoding 0o777 is a security risk. Instead we can use 0770 for better security. |
I would recommend to set default as 0o770 and allow customization in parameters. |
@leptonyu Can you update the the description and what is your expectation in the issue description. So that it will be easy to the contributor to contribute. |
Done |
How would this interact with the fact volumes do not respect fsGroup and cannot have their owners changed by an InitContainer? |
Customizing Settings could be configured as 777 to keep as-is, or design matched user/group to run Pod. |
I am not involved in this discussion but what i think is giving permission 0o777 will not be good the issue is correct instead if we permit it to the 0o770 atleast we are targeting to the most. And Here customizing will be good as if you want to give full permission then you can. |
Description:
Current design hardcode folder permission as
0o777
.nfs-subdir-external-provisioner/cmd/nfs-subdir-external-provisioner/provisioner.go
Line 115 in 59a3ca2
Request:
0o770
.The text was updated successfully, but these errors were encountered: