-
Notifications
You must be signed in to change notification settings - Fork 545
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
Run the controller in non-privileged mode #1050
Comments
I have the same question |
Hi @mauriciopoppe, thanks for bringing here. Yes, it does not need to run as privileged, will raise a PR and mark in the next release. |
The latest version 1.5.8 has the updated the security context. |
/close |
@mskanth972: Closing this issue. In response to this:
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. |
I saw these lines in the controller deployment
aws-efs-csi-driver/deploy/kubernetes/base/controller-deployment.yaml
Lines 36 to 37 in e914558
Does it need to run as privileged? From my understanding the node plugin is the one that might be doing format/mount which are privileged storage operations but the controller would only be making cloud requests. Could we remove it safely?
The text was updated successfully, but these errors were encountered: