-
Notifications
You must be signed in to change notification settings - Fork 219
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
Pod Security policy feature for k8s version 1.29 #923
Comments
As a driver (vs. a "normal" app), Trident will need specific privileges for operations such as mounting/unmounting volumes on the nodes. As Pod Security Policies are deprecated/removed since many K8s releases, Trident set the required Pod Security Standard Not exactly sure what you are trying to change, that should be surfaced in the Helm chart? |
Hello,
We are trying to follow the security best practices in which a pod/container should not run as root.
Considering this, we are trying to install the trident helm chart on k8s version 1.29 and we don't have the posibility to set the pod/container security policy via the values file.
In order to use the helm chart smoothly and perform upgrades we belive that we should have this option integrated into the values file.
Thanks in advance.
Leonard Poiana
DevOps Engineer
The text was updated successfully, but these errors were encountered: