RBAC: keep the rights to the "list" of secrets and restrict the "list" of several secrets by name

I have an operator whose code is not accessible
By default, the operator requires the rights to list all secrets with no "resource Names" restriction
I can't grant such rights. Is there anyway to keep the rights to list all secrets and prohibit list multiple secrets by name

I tried to give rights to the list with resourceNames, but the operator does not accept this behavior and writes an error on startup

failed to list v1.Secret: secrets is forbidden: User "system:serviceaccount:operator-*****" cannot list resource "secrets" in API group "" in the namespace "namespace-name"

failed to list v1.Secret: secrets is forbidden: User "system:serviceaccount:operator-*****" cannot list resource "secrets" in API group "" in the namespace "namespace-name"

The above error states that the operator with a service account does not have permission to list the secrets, to resolve your issue create role binding for service account as it not given access by default after creation, for adding a viewer (read only) role to service account run the following command:

For example, grant read-only permission within "my-namespace" to the "my-sa" service account:

kubectl create rolebinding my-sa-view \

 --clusterrole=view \

 --serviceaccount=my-namespace:my-sa \

 --namespace=my-namespace

Found a similar stack question for more information.