You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
bsamsom
changed the title
Tighten RBAC policies on the trident-operator service account.
Tighten RBAC policies on the trident service accounts.
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 noresourceNames
.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 asingular namespace
, or setresourceNames
to the secrets it need access to, so that the service account only has access to the secrets it needs.The text was updated successfully, but these errors were encountered: