<p>I have the following <code>RoleBinding</code> (it was deployed by Helm:</p>
<pre><code>apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  annotations:
    meta.helm.sh/release-name: environment-namespaces
    meta.helm.sh/release-namespace: namespace-metadata
  creationTimestamp: &quot;2021-04-23T17:16:50Z&quot;
  labels:
    app.kubernetes.io/managed-by: Helm
  name: SA-DevK8s-admin
  namespace: dev-my-product-name-here
  resourceVersion: &quot;29221536&quot;
  selfLink: /apis/rbac.authorization.k8s.io/v1/namespaces/dev-my-product-name-here/rolebindings/SA-DevK8s-admin
  uid: 4818d6ed-9320-408c-82c3-51e627d9f375
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: admin
subjects:
- apiGroup: rbac.authorization.k8s.io
  kind: User
  name: SA-DevK8s@mydomain.com
</code></pre>
<p>When I login to the cluster as <code>SA-DevK8s@mydomain.com</code> and run <code>kubectl get pods -n dev-my-product-name-here</code> it get the following error:</p>
<blockquote>
<p>Error from server (Forbidden): pods is forbidden: User &quot;sa-devk8s@mydomain.com&quot; cannot list resource &quot;pods&quot; in API group &quot;&quot; in the namespace &quot;dev-my-product-name-here&quot;</p>
</blockquote>
<p><strong>Shouldn't a user who has the ClusterRole of admin in a namespace be able to list the pods for that namespace?</strong></p>

Vaccano
<p><strong>Case Matters!!!!</strong></p>
<p>Once I changed the user to be <code>sa-devk8s@mydomain.com</code> (instead of <code>SA-DevK8s@mydomain.com</code>), it all started working correctly!</p>
