<p>After I deployed the webui (k8s dashboard), I logined to the dashboard but nothing found there, instead a list of errors in notification.</p>
<pre><code>tatefulsets.apps is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;statefulsets&quot; in API group &quot;apps&quot; in the namespace &quot;default&quot; 2 minutes ago
error
replicationcontrollers is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;replicationcontrollers&quot; in API group &quot;&quot; in the namespace &quot;default&quot; 2 minutes ago
error
replicasets.apps is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;replicasets&quot; in API group &quot;apps&quot; in the namespace &quot;default&quot; 2 minutes ago
error
deployments.apps is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;deployments&quot; in API group &quot;apps&quot; in the namespace &quot;default&quot; 2 minutes ago
error
jobs.batch is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;jobs&quot; in API group &quot;batch&quot; in the namespace &quot;default&quot; 2 minutes ago
error
events is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;events&quot; in API group &quot;&quot; in the namespace &quot;default&quot; 2 minutes ago
error
pods is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;pods&quot; in API group &quot;&quot; in the namespace &quot;default&quot; 2 minutes ago
error
daemonsets.apps is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;daemonsets&quot; in API group &quot;apps&quot; in the namespace &quot;default&quot; 2 minutes ago
error
cronjobs.batch is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;cronjobs&quot; in API group &quot;batch&quot; in the namespace &quot;default&quot; 2 minutes ago
error
namespaces is forbidden: User &quot;system:serviceaccount:kubernetes-dashboard:default&quot; cannot list resource &quot;namespaces&quot; in API group &quot;&quot; at the cluster scope
</code></pre>
<p>Here is all my pods</p>
<pre><code>NAMESPACE              NAME                                         READY   STATUS    RESTARTS   AGE   IP               NODE             NOMINATED NODE   READINESS GATES
kube-system            calico-kube-controllers-58497c65d5-828dm     1/1     Running   0          64m   10.244.192.193   master-node1     &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-dblzp                            1/1     Running   0          17m   157.245.57.140   cluster3-node1   &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-dwdvh                            1/1     Running   1          49m   157.245.57.139   cluster2-node2   &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-gskr2                            1/1     Running   0          17m   157.245.57.133   cluster1-node2   &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-jm5rd                            1/1     Running   0          17m   157.245.57.144   cluster4-node2   &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-m8htd                            1/1     Running   0          17m   157.245.57.141   cluster3-node2   &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-n7d44                            1/1     Running   0          64m   157.245.57.146   master-node1     &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-wblpr                            1/1     Running   0          17m   157.245.57.135   cluster2-node1   &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-wbrzf                            1/1     Running   1          29m   157.245.57.136   cluster1-node1   &lt;none&gt;           &lt;none&gt;
kube-system            calico-node-wqwkj                            1/1     Running   0          17m   157.245.57.142   cluster4-node1   &lt;none&gt;           &lt;none&gt;
kube-system            coredns-78fcd69978-cnzxv                     1/1     Running   0          64m   10.244.192.194   master-node1     &lt;none&gt;           &lt;none&gt;
kube-system            coredns-78fcd69978-f4ln8                     1/1     Running   0          64m   10.244.192.195   master-node1     &lt;none&gt;           &lt;none&gt;
kube-system            etcd-master-node1                            1/1     Running   1          64m   157.245.57.146   master-node1     &lt;none&gt;           &lt;none&gt;
kube-system            kube-apiserver-master-node1                  1/1     Running   1          64m   157.245.57.146   master-node1     &lt;none&gt;           &lt;none&gt;
kube-system            kube-controller-manager-master-node1         1/1     Running   1          64m   157.245.57.146   master-node1     &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-2b5bz                             1/1     Running   0          17m   157.245.57.144   cluster4-node2   &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-cslwc                             1/1     Running   3          49m   157.245.57.139   cluster2-node2   &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-hlvxc                             1/1     Running   0          17m   157.245.57.140   cluster3-node1   &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-kkdqn                             1/1     Running   0          17m   157.245.57.142   cluster4-node1   &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-sm7nq                             1/1     Running   0          17m   157.245.57.133   cluster1-node2   &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-wm42s                             1/1     Running   0          64m   157.245.57.146   master-node1     &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-wslxd                             1/1     Running   0          17m   157.245.57.141   cluster3-node2   &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-xnh24                             1/1     Running   0          17m   157.245.57.135   cluster2-node1   &lt;none&gt;           &lt;none&gt;
kube-system            kube-proxy-zvsqf                             1/1     Running   1          29m   157.245.57.136   cluster1-node1   &lt;none&gt;           &lt;none&gt;
kube-system            kube-scheduler-master-node1                  1/1     Running   1          64m   157.245.57.146   master-node1     &lt;none&gt;           &lt;none&gt;
kubernetes-dashboard   dashboard-metrics-scraper-856586f554-c4thn   1/1     Running   0          14m   10.244.14.65     cluster2-node2   &lt;none&gt;           &lt;none&gt;
kubernetes-dashboard   kubernetes-dashboard-67484c44f6-hwvj5        1/1     Running   0          14m   10.244.213.65    cluster1-node1   &lt;none&gt;           &lt;none&gt;

</code></pre>
<p>Here is all my nodes:</p>
<pre><code>NAME             STATUS   ROLES                  AGE   VERSION
cluster1-node1   Ready    &lt;none&gt;                 29m   v1.22.1
cluster1-node2   Ready    &lt;none&gt;                 17m   v1.22.1
cluster2-node1   Ready    &lt;none&gt;                 17m   v1.22.1
cluster2-node2   Ready    &lt;none&gt;                 49m   v1.22.1
cluster3-node1   Ready    &lt;none&gt;                 17m   v1.22.1
cluster3-node2   Ready    &lt;none&gt;                 17m   v1.22.1
cluster4-node1   Ready    &lt;none&gt;                 17m   v1.22.1
cluster4-node2   Ready    &lt;none&gt;                 17m   v1.22.1
master-node1     Ready    control-plane,master   65m   v1.22.1
</code></pre>
<p>I suspect there is misconfiguration in kubernetes-dashboard namespace, so it cannot access the system.</p>

<p>I have recreated the situation according to the attached tutorial and it works for me.
Make sure, that you are <a href="https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/#accessing-the-dashboard-ui" rel="noreferrer">trying properly login</a>:</p>
<blockquote>
<p>To protect your cluster data, Dashboard deploys with a minimal RBAC configuration by default. Currently, Dashboard only supports logging in with a Bearer Token. To create a token for this demo, you can follow our guide on  <a href="https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/creating-sample-user.md" rel="noreferrer">creating a sample user</a>.</p>
<p><strong>Warning:</strong>  The sample user created in the tutorial will have administrative privileges and is for educational purposes only.</p>
</blockquote>
<p>You can also create <code>admin role</code>:</p>
<pre class="lang-yaml prettyprint-override"><code>kubectl create clusterrolebinding serviceaccounts-cluster-admin \
  --clusterrole=cluster-admin \
  --group=system:serviceaccounts
</code></pre>
<p><strong>However, you need to know that this is potentially a very dangerous solution as you are granting root permissions to create pods for every user who has read secrets. You should use this method only for learning and demonstrating purpose.</strong></p>
<p>You can read more about this solution <a href="https://stackoverflow.com/a/49174177/15407542">here</a> and more about <a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/" rel="noreferrer">RBAC authorization</a>.</p>
<p>See also <a href="https://stackoverflow.com/questions/47973570/kubernetes-log-user-systemserviceaccountdefaultdefault-cannot-get-services">this question</a>.</p>
