$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-547fb75957-qj4ll 1/1 Running 0 2d23h
kube-system calico-node-7h4rj 1/1 Running 0 2d23h
kube-system coredns-7776bd96f-d5jbr 1/1 Running 0 2d23h
kube-system coredns-7776bd96f-kzw68 1/1 Running 0 2d23h
kube-system etcd-ap-rhoek8c.oneadr.net 1/1 Running 6 2d23h
kube-system kube-apiserver-ap-rhoek8c.oneadr.net 1/1 Running 6 2d23h
kube-system kube-controller-manager-ap-rhoek8c.oneadr.net 1/1 Running 11 2d23h
kube-system kube-proxy-r4v2t 1/1 Running 0 2d23h
kube-system kube-scheduler-ap-rhoek8c.oneadr.net 1/1 Running 11 2d23h
kube-system metrics-server-74d7f54fdc-qr2v2 0/1 Pending 0 2d23h
kubernetes-dashboard dashboard-metrics-scraper-55b6f68dd5-svhdm 1/1 Running 2 2d23h
kubernetes-dashboard kubernetes-dashboard-6d4f55d9d6-7bs47 1/1 Running 2 2d23hkubectl apply -f dashboard-adminuser.yaml && kubectl apply -f cluster-role-binding.yaml{ "kind": "Status", "apiVersion": "v1", "metadata": { }, "status": "Failure", "message": "services \"https:metrics-server:\" is forbidden: User \"system:anonymous\" cannot get resource \"services/proxy\" in API group \"\" in the namespace \"kube-system\"", "reason": "Forbidden", "details": { "name": "https:metrics-server:", "kind": "services" }, "code": 403 } What I have missed to set up? Thank you in advance for your time and effort. BR
$ kubectl -n kubernetes-dashboard describe secret $(kubectl -n kubernetes-dashboard get secret | grep admin-user | awk '{print $1}')
Name: admin-user-token-rkjlt
Namespace: kubernetes-dashboard
Labels: <none>
Annotations: kubernetes.io/service-account.name: admin-user
kubernetes.io/service-account.uid: 4a05a0c3-089d-426d-8f01-4e1f6eab3e36
Type: kubernetes.io/service-account-tokenData
====
token: <my_token>
ca.crt: 1025 bytes
namespace: 20 byteskubectl apply -f dashboard-adminuser.yaml{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "services \"https:metrics-server:\" is forbidden: User \"system:anonymous\" cannot get resource \"services/proxy\" in API group \"\" in the namespace \"kube-system\"",
"reason": "Forbidden",
"details": {
"name": "https:metrics-server:",
"kind": "services"
},
"code": 403
}
I can see that the metrics-server container has not started yet but I am not able to understand as to what I have missed. I have spend time online looking for questions / answers but I can not figure it out. I am running on kubernetes 1.18.2:$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:48:36Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Sample of all pods together: $ kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system calico-kube-controllers-547fb75957-qj4ll 1/1 Running 0 2d20h kube-system calico-node-7h4rj 1/1 Running 0 2d20h kube-system coredns-7776bd96f-d5jbr 1/1 Running 0 2d20h kube-system coredns-7776bd96f-kzw68 1/1 Running 0 2d20h kube-system etcd-ap-rhoek8c.oneadr.net 1/1 Running 6 2d20h kube-system kube-apiserver-ap-rhoek8c.oneadr.net 1/1 Running 6 2d20h kube-system kube-controller-manager-ap-rhoek8c.oneadr.net 1/1 Running 11 2d20h kube-system kube-proxy-r4v2t 1/1 Running 0 2d20h kube-system kube-scheduler-ap-rhoek8c.oneadr.net 1/1 Running 11 2d20h kube-system metrics-server-74d7f54fdc-qr2v2 0/1 Pending 0 2d20h kubernetes-dashboard dashboard-metrics-scraper-55b6f68dd5-svhdm 1/1 Running 2 2d20h kubernetes-dashboard kubernetes-dashboard-6d4f55d9d6-7bs47 1/1 Running 2 2d20h Any hits would be greatly appreciated.