1. Proposed title of this feature request
Looking for an option to exclude few namespaces in rolebinding. Or an option to include multiple namespaces in a rolebinding.

2. What is the nature and description of the request?

3. Why does the customer need this? (List the business requirements here)
Customer wants to create a rolebinding for clusterrole. They are assigning access to service account on 80+ namespaces, but not all.
It is difficult to create rolebinding in every namespace (for 80+ namespaces). Hence, they are looking for an option to exclude few namespaces and assign access on all other namespaces.

4. List any affected packages or components.

Steps to reproduce :
1 Create project1.
2 Create a Service account in project1.
3 Create a Clusterrole with verb=get,watch,list resource=pods
4 Create a local rolebinding in project2 with clusterrole assigned to service account (created in project1).
[with above steps service account created in project1 will get get,watch,list pod access in project2]

To assign clusterrole to service account for a specific project, we need to create a local rolebinding in that project.
Customer wants to assign this clusterrole to service account in many projects (but not all).

We are looking for an option to exclude few namespaces in a rolebinding. Or an option to include multiple namespaces in a rolebinding.