kubectl cluster-info not showing "kubernetes-dashboard is running at"

[mhabicht]

I am not sure why my dashboard is not coming up.

kubectl cluster-info

Kubernetes master is running at https://10.243.90.102:6443
KubeDNS is running at https://10.243.90.102:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

I have configured my dashboard and all is running.

kubectl get all --namespace=kube-system

NAME READY STATUS RESTARTS AGE
pod/etcd-ucs1 1/1 Running 1 1h
pod/kube-apiserver-ucs1 1/1 Running 1 1h
pod/kube-controller-manager-ucs1 1/1 Running 1 1h
pod/kube-dns-86f4d74b45-f4cs9 3/3 Running 3 1h
pod/kube-proxy-ntjnc 1/1 Running 1 1h
pod/kube-proxy-ztstt 1/1 Running 0 1h
pod/kube-scheduler-ucs1 1/1 Running 1 1h
pod/kubernetes-dashboard-7d5dcdb6d9-rd6lt 1/1 Running 0 1h
pod/weave-net-gp58g 2/2 Running 0 1h
pod/weave-net-r5x92 2/2 Running 3 1h

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kube-dns ClusterIP 10.96.0.10 53/UDP,53/TCP 1h
service/kubernetes-dashboard ClusterIP 10.98.146.95 443/TCP 1h

NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/kube-proxy 2 2 2 2 2 1h
daemonset.apps/weave-net 2 2 2 2 2 1h

NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deployment.apps/kube-dns 1 1 1 1 1h
deployment.apps/kubernetes-dashboard 1 1 1 1 1h

NAME DESIRED CURRENT READY AGE
replicaset.apps/kube-dns-86f4d74b45 1 1 1 1h
replicaset.apps/kubernetes-dashboard-7d5dcdb6d9 1 1 1 1h

What am I missing or what did I not start?

[ishanupadhyay]

is it showing connection timeout? can you tell me your kubernetes version which is in cluster yaml file?

[mhabicht]

kubectl logs -n kube-system kubernetes-dashboard-7d5dcdb6d9-rd6lt | more
2018/05/22 12:41:45 Starting overwatch
2018/05/22 12:41:45 Using in-cluster config to connect to apiserver
2018/05/22 12:41:45 Using service account token for csrf signing
2018/05/22 12:41:45 No request provided. Skipping authorization
2018/05/22 12:41:45 Successful initial request to the apiserver, version: v1.10.3
2018/05/22 12:41:45 Generating JWE encryption key
2018/05/22 12:41:45 New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Star
ting
2018/05/22 12:41:45 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-syst
em
2018/05/22 12:41:46 Storing encryption key in a secret
2018/05/22 12:41:46 Creating in-cluster Heapster client
2018/05/22 12:41:46 Auto-generating certificates
2018/05/22 12:41:46 Successfully created certificates
2018/05/22 12:41:46 Serving securely on HTTPS port: 8443
2018/05/22 12:41:46 Metric client health check failed: the server could not find the requested resource (ge
t services heapster). Retrying in 30 seconds.

kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:05:37Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

[floreks]

As per the documentation: https://kubernetes-v1-4.github.io/docs/user-guide/kubectl/kubectl_cluster-info/

Display addresses of the master and services with label kubernetes.io/cluster-service=true

By default Dashboard does not have such label, thus it is not visible as a cluster service.

[mhabicht]

I found the answer. Running this will bring up my dashboard service without needing kubectl proxy

kubectl create secret generic kubernetes-dashboard-certs --from-file=$HOME/certs -n kube-system

[anirtek]

try minikube -p cluster-name dashboard