Azure
acs-engine
Kubernetes 1.10.2
Dashboard version:
latest
Kubernetes version:
1.10.2
Operating system:
linux/amd64
Node.js version:
Unknown
Go version:
go1.9.3
Successfully installed Kubernetes 1.10.2 using acs-engine on Azure
kubectl cluster-info
Kubernetes master is running at https://10.246.7.100:443
Heapster is running at https://10.246.7.100:443/api/v1/namespaces/kube-system/services/heapster/proxy
KubeDNS is running at https://10.246.7.100:443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
kubernetes-dashboard is running at https://10.246.7.100:443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy
Metrics-server is running at https://10.246.7.100:443/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
tiller-deploy is running at https://10.246.7.100:443/api/v1/namespaces/kube-system/services/tiller-deploy:tiller/proxy
Followed steps under https://github.com/kubernetes/dashboard/blob/master/README.md
Error: 'dial tcp 10.244.1.41:9090: getsockopt: connection timed out'
Trying to reach: 'https://10.244.1.41:9090/'
Dashboard main page
Same problem here, my environment:
Platform: Azure
Deployment: acs-engine
Versions:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-05-12T04:12:12Z", GoVersion:"go1.9.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:10:24Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Steps to reproduce
Successfully installed Kubernetes 1.10.2 using acs-engine on Azure:
$ kubectl cluster-info
Kubernetes master is running at https://<REDACTED>.cloudapp.azure.com
KubeDNS is running at https://<REDACTED>.cloudapp.azure.com/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
kubernetes-dashboard is running at https://<REDACTED>.cloudapp.azure.com/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy
Metrics-server is running at https://<REDACTED>.cloudapp.azure.com/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
tiller-deploy is running at https://<REDACTED>.cloudapp.azure.com/api/v1/namespaces/kube-system/services/tiller-deploy:tiller/proxy
Followed steps under https://github.com/kubernetes/dashboard/blob/master/README.md:
Run
$ kubectl proxy
Then opened this url on my browser http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/
Observed result
Error: 'dial tcp 10.244.0.9:8443: getsockopt: connection timed out'
Trying to reach: 'https://10.244.0.9:8443/'
same problem here with kubernetes v1.10.3, dashboard v1.8.3.
http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/
outputs:
Error: 'net/http: TLS handshake timeout'
Trying to reach: 'https://10.244.1.144:8443/'
but if changed it to
http://localhost:8001/api/v1/namespaces/kube-system/services/http:kubernetes-dashboard:/proxy/, it shows:
Error: 'net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x15\x03\x01\x00\x02\x02"'
Trying to reach: 'http://10.244.1.144:8443/'
So the service must be normal.
any update on this issue?
master install flannel
I am experiencing the same issue with Kubernetes 1.10.4
Finally reinstall recommended docker version 17.03 fixed my problem.
same problem here too
same problem, how do we resolve?
Unfortunately you have to wait for the next release when we will introduce changes allowing to use it with Kubernetes 1.10.
kubectl --namespace=kube-system port-forward kubernetes-dashboard-5bd6f767c7-8bhkf 8443
https://127.0.0.1:8443/
works for me
Same problem with Kubernetes v1.11.0. Port forward temporary solve the issue. Thanks @alien2003
Release https://github.com/kubernetes/dashboard/releases/tag/v1.10.0 fixes that problem:
https://github.com/kubernetes/dashboard/wiki/Compatibility-matrix
/close
@maciaszczykm: Closing this issue.
In response to this:
Release https://github.com/kubernetes/dashboard/releases/tag/v1.10.0 fixes that problem:
https://github.com/kubernetes/dashboard/wiki/Compatibility-matrix
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Most helpful comment
kubectl --namespace=kube-system port-forward kubernetes-dashboard-5bd6f767c7-8bhkf 8443
https://127.0.0.1:8443/
works for me