New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K8s dashboard showing "no healthy upstream"; remove K8s dashboard links and services #1699
Comments
+1 |
Should we just get rid of the link to the K8s dashboard and let users take care of it using the appropriate solution for their K8s distribution. This has never worked particularly well because the dashboard is not easy to authenticate to (on GKE you had to print an access token and then past it in). I also think the dashboard has been deprecated and removed on GKE and possibly others. /area 0.4.0 /cc @swiftdiaries |
* The K8s dashboard is not always installed; so just adding a link to it leads to confusion because it may not actually be present. * Furthermore, even when the dashboard is running there might not be a convenient way to authenticate to it short of having users generate and paste access tokens. Fix kubeflow#1699
* The K8s dashboard is not always installed; so just adding a link to it leads to confusion because it may not actually be present. * Furthermore, even when the dashboard is running there might not be a convenient way to authenticate to it short of having users generate and paste access tokens. Fix #1699
* The K8s dashboard is not always installed; so just adding a link to it leads to confusion because it may not actually be present. * Furthermore, even when the dashboard is running there might not be a convenient way to authenticate to it short of having users generate and paste access tokens. Fix kubeflow#1699
* The K8s dashboard is not always installed; so just adding a link to it leads to confusion because it may not actually be present. * Furthermore, even when the dashboard is running there might not be a convenient way to authenticate to it short of having users generate and paste access tokens. Fix kubeflow#1699
This is configured as:
However there is no such service in the kube-system namespace:
ricliu@ricliu:~/kubeflow/kubeflow$ kubectl -n kube-system get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default-http-backend NodePort 10.3.254.180 80:30631/TCP 12h
heapster ClusterIP 10.3.250.231 80/TCP 12h
kube-dns ClusterIP 10.3.240.10 53/UDP,53/TCP 12h
metrics-server ClusterIP 10.3.250.4 443/TCP 12h
The text was updated successfully, but these errors were encountered: