<p>We have multiple Namespaces in our cluster. Admin will have access to all the Namespaces by means of ClusterRole. But, user will be given access to the corresponding namespaces.</p>
<p>Say, user A is given access to namespace B,C &amp; D.</p>
<p>So user A deploys dashboard in Namespace B with service account and RoleBinding. User will be able to see all the applications in Namespaces B. But, how can we give access to this Dashboard so that one dashboard will be listing the 3 Namespaces to see the corresponding applications?</p>

user1578872
<p>In the current version of <a href="https://kubernetes.io" rel="nofollow noreferrer">Kubernetes</a>, it is possible to manage different namespaces by different users.
You need to realize how the <a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/" rel="nofollow noreferrer">RBAC</a> works and how to use it to manage multiple <a href="https://github.com/kubernetes/dashboard" rel="nofollow noreferrer">Dashboards</a>.</p>

<p>Draft of the concept: You need to create rules, roles and grant permission (cluster-wide and all namespaces) and then do rolebinding.
It can be used to grant read access to resources in any particular namespace, or across all namespaces.</p>

<p>For example, here is how to bind user "jane" to the default namespace and user "dave" to the development team.
You can provide Dashboard in both namespaces to give individual user access to them.</p>

<pre><code># This role binding allows "jane" to read pods in the "default" namespace.
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: read-pods
  namespace: default
subjects:
- kind: User
  name: jane # Name is case sensitive
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: Role #this must be Role or ClusterRole
  name: pod-reader # this must match the name of the Role or ClusterRole you wish to bind to
  apiGroup: rbac.authorization.k8s.io

   # This role binding allows "dave" to read secrets in the "development" namespace.
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: read-secrets
  namespace: development # This only grants permissions within the "development" namespace.
subjects:
- kind: User
  name: dave # Name is case sensitive
  apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: ClusterRole
  name: secret-reader
  apiGroup: rbac.authorization.k8s.io
</code></pre>
