A user can have many permissions in his/her own namespace without compromising the other tenants. This sounds like it would allow any user with Ingress create/update access in any namespace to compromise secrets across all namespaces.
there's definitely an attack path that gets the ingress-nginx service account token, which has list rights on secrets at a cluster level (so allowing for all secret values to be retrieved).
[0] https://github.com/kubernetes/ingress-nginx/issues/7837#issu...
I'm afraid not. HTTP GET on a collection endpoint (which is the operation represented by the list verb) returns the full object content.
https://kubernetes.io/docs/reference/access-authn-authz/auth...