DBCL
DBCL

Reputation: 91

Kubernetes-dashboard empty : every resources are forbidden

It seems I have a very common problem but I cannot figure it out.

On a new kubernetes cluster (v1.17) I'm trying to install Kubernetes-dashboard.

For this I followed the official steps, starting by installing the dashboard :

kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-rc5/aio/deploy/recommended.yaml

Then I created the ServiceAccount

apiVersion: v1
kind: ServiceAccount
metadata:
  name: admin-user
  namespace: kubernetes-dashboard

And the ClusterRoleBinding

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: admin-user
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: admin-user
  namespace: kubernetes-dashboard

Everything is running smoothly and all the objets get created (I can get them and everything looks alright)

After running kubectl proxy the dashboard is accessible at this URL :

http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/

Then I enter the token I got with this command :

kubectl -n kubernetes-dashboard describe secret $(kubectl -n kubernetes-dashboard get secret | grep admin-user-token | awk '{print $1}')

I can login, but the dashboard is empty. The notifications panel is full of

[OBJECT] is forbidden: User "system:serviceaccount:kubernetes-dashboard:admin-user" cannot list resource "[OBJECT]" in API group "extensions" in the namespace "default"

Replace [OBJECT] with every kubernetes object and you have a good overview of my notifications panel ;)

The admin-user has obviously not enough rights to access the objects.

Questions

Thank you for your help !

Edit: That was an outage from my cloud provider. I don't know what happened nor how they solved it but they did something and everything is working now.

Upvotes: 1

Views: 4926

Answers (2)

alparslan
alparslan

Reputation: 173

role binding give this error?

The ClusterRoleBinding "kubernetes-dashboard" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"ClusterRole", Name:"cluster-admin"}: cannot change roleRef

Upvotes: 1

DBCL
DBCL

Reputation: 91

In the end, that was an outage from the cloud provider. I ran into another problem with PVC, they solved it and tadaa the dashboard is working just fine with no modifications.

Upvotes: 1

Related Questions