<p>I do understand RBAC and I'm able to create a role using rules en subjects, bind them with a user.</p>

<p>For example this role can only list the pods</p>

<pre><code>kind: Role
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  namespace: development
  name: list-pods
rules:
- apiGroups: [""] # "" indicates the core API group
  resources: ["pods"]
  verbs: ["get", "list"]
</code></pre>

<p>Now we are using namespaces for every environment we have (dev, staging, prd). Now how do I have to provide this role to users in different namespaces? Do I have to create a clusterRole and bind it with a normal rolebinding or do I have to write the above .yaml once for dev, once for uat and once for prd? Are there somewhere rules written about how to handles those cases? </p>

DenCowboy
<p>In your specific case I would create a single cluster role with the desired permissions and then bind it via role bindings to the appropriate subjects in the relevant namespaces.</p>
