dashboard: dashboard not working with https

https://github.com/kubernetes/dashboard/wiki/Accessing-dashboard

To make a long story short - BEFORE authentication, the /ui redirect will not work. Go here instead and it will ask you to authenticate: http://127.0.0.1:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login

It should redirect here after login: http://127.0.0.1:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

Thanks to @rama-arun for the link.

I can connect via https://<master-ip>:<apiserver-port>/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/ but browser still warns about unsecure connection

Do not use /ui redirect as it has not been updated yet. Our main README and Acessing Dashboard guide on wiki pages have correct link to Dashboard. Read them please.

• Make sure kubernetes is running with minikube or Docker for Windows/Mac, etc.
• Check kubectl version
• Download a dashboard file: curl -O https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml
• Load kubectl apply -f kubernetes-dashboard.yaml
• Run dashboard kubectl proxy
• Go to the login page and select Token option:
• (Link1) http://127.0.0.1:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login
• Generate token with kubectl: kubectl -n kube-system get secret
• Look for something like this:

deployment-controller-token-fwwd4     kubernetes.io/service-account-token   3  9d

• Run kubectl -n kube-system describe secret deployment-controller-token-fwwd4 (your last 5 letters will be different, not fwwd4)
• Copy the generated token and paste it in (Link1)
• Go to dashboard :
• (Link2) http://127.0.0.1:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/overview?namespace=default

Source: (Link3) https://stackoverflow.com/questions/46664104/how-to-sign-in-kubernetes-dashboard

I’ve done that already. Please check my last post(#issuecomment-337165510).

---

Sorry, the only difference between #issuecomment-337165510 is this test based on https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml and #issuecomment-337165510 based on https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/alternative/kubernetes-dashboard.yaml . In post #issuecomment-337165510 , /ui can be accessed but accessing resources is forbidden.

---

1. Remove old resources(kubectl delete -f kubernetes-dashboard.yaml) and make sure old dashboard pod has already been destroyed(kubectl -n kube-system get pods won’t show it already);
2. Create everything as kubernetes-dashboard.yaml(kubectl apply -f kubernetes-dashboard.yaml);
3. Make sure dashboard pod has already been created and started(kubernetes-dashboard-79d9896c7b-bfrwr 1/1 Running 0 7s)
4. Start my proxy sudo kubectl --kubeconfig $HOME/.kube/config proxy --port 80
5. Open my browser and point it to http://127.0.0.1/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/, shows Error: 'net/http: TLS handshake timeout' Trying to reach: 'https://10.244.0.11:8443/'
6. Try to access /ui and the location was redirected to http://127.0.0.1/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/ and told me Error: 'malformed HTTP response "\x15\x03\x01\x00\x02\x02"' Trying to reach: 'http://10.244.0.10:8443/'

My last post is trying to resolve the problem of forbidden access of resources, in which you told me there are no flags of --tls-cert-file and --tls-key-file provided. However, I thought copying apiserver.{crt,key} as dashboard.{crt,key} and creating kubernetes-dashboard-certs manully would solve this problem, but it is not. Isn’t it what you are mean? And what should be the right solution for supply these flags?

BTW, kubernetes-dashboard.yaml is freshly downloaded from https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml supplied in README.md

@floreks @cheld Ok, thanks a lot! However, it tolds me handshake timeout. Actually I’m reusing /etc/kubernetes/pki/front-proxy-client.crt and /etc/kubernetes/pki/front-proxy-client.key as its certs according to https://github.com/kubernetes/dashboard/wiki/Installation#recommended-setup .

My steps are(I just want to reuse these keys instead of generating new keys manually):

cp /etc/kubernetes/pki/front-proxy-client.crt $HOME/certs/dashboard.crt
cp /etc/kubernetes/pki/front-proxy-client.key $HOME/certs/dashboard.key
kubectl create secret generic kubernetes-dashboard-certs --from-file=$HOME/certs -n kube-system
kubectl apply -f https://github.com/kubernetes/dashboard/wiki/Installation#recommended-setup
kubectl --kubeconfig $HOME/.kube/config proxy --port 80

When I trying to access http://127.0.0.1/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/, it tells me like this:

Error: 'net/http: TLS handshake timeout'
Trying to reach: 'https://10.244.0.6:8443/'

I guess it’s a problem about certificate, I’ve no idea what’s wrong with it. Could you guys please give me some suggestion? Thanks a head!