Skip to content
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

Tighten RBAC policies on the trident service accounts. #897

Open
bsamsom opened this issue Apr 1, 2024 · 0 comments
Open

Tighten RBAC policies on the trident service accounts. #897

bsamsom opened this issue Apr 1, 2024 · 0 comments

Comments

@bsamsom
Copy link

bsamsom commented Apr 1, 2024

The trident helm chart grants the trident-operator service account access to every secret in kuberentes.

This is because it uses a ClusterRole with no resourceNames.
https://github.com/NetApp/trident/blob/master/helm/trident-operator/templates/clusterrole.yaml#L60-L71

For better security the helm chart should either use a Role and restrict the secret access to a singular namespace, or set resourceNames to the secrets it need access to, so that the service account only has access to the secrets it needs.

@bsamsom bsamsom changed the title Tighten RBAC policies on the trident-operator service account. Tighten RBAC policies on the trident service accounts. Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants