Sebastian Florek edited this page Dec 19, 2017 · 38 revisions

In case you did not find any answer here and in closed issues, create new issue.

I would like to use development environment on HTTPS, how to do it?

Development environment is started with gulp serve or gulp serve:prod. To make it run on HTTPS it needs to have certificates passed. To do it you need to use following flags for mentioned commands:

  • tlsCert - path to .crt file
  • tlsKey - path to .key file
  • serveHttps - flag to enable HTTPS mode

Dashboard is throwing open /certs/dashboard.crt: no such file or directory error.

It was fixed in 1.8.0 release and should not happen anymore.

This happens from time to time. Init container used to create self-signed certs has not finished its job and main Dashboard container has been started without required certificates. Try redeploy Dashboard, it should fix the issue.

I cannot see any graphs in Dashboard, how to enable them?

Make sure, that Heapster is up and running and Dashboard was able to connect with it. First you have to verify Heapster state with Dashboard or kubectl command. Then you should check Dashboard logs and look for metric and Heapster keywords. You can find more informations about Dashboard's Integrations here.

During development I receive a lot of strange errors in the browser's console. What may be wrong?

You probably need to update your npm dependencies. Run following commands from Dashboard's root directory:

rm -rf node_modules && npm i

Why my Go is not in the path?

Running into an error like that probably means, that you need to rerun following command:

export PATH=$PATH:/usr/local/go/bin

I receive linux mounts: Path /var/lib/kubelet is mounted on / but it is not a shared mount error. What to do?

Try to run:

sudo mount --bind /var/lib/kubelet /var/lib/kubelet && sudo mount --make-shared /var/lib/kubelet

You can find more information here.

I am seeing 404 errors when trying to access Dashbord. Dashboard resources can not be loaded.

GET https://<IP>/api/v1/namespaces/kube-system/services/kubernetes-dashboard/static/vendor.9aa0b786.css 
proxy:1 GET https://<IP>/api/v1/namespaces/kube-system/services/kubernetes-dashboard/static/app.8ebf2901.css 
proxy:5 GET https://<IP>/api/v1/namespaces/kube-system/services/kubernetes-dashboard/api/appConfig.json 
proxy:5 GET https://<IP>/api/v1/namespaces/kube-system/services/kubernetes-dashboard/static/app.68d2caa2.js 
proxy:5 GET https://<IP>/api/v1/namespaces/kube-system/services/kubernetes-dashboard/static/vendor.840e639c.js 
proxy:5 GET https://<IP>/api/v1/namespaces/kube-system/services/kubernetes-dashboard/api/appConfig.json 
proxy:5 GET https://<IP>/api/v1/namespaces/kube-system/services/kubernetes-dashboard/static/app.68d2caa2.js

IMPORTANT: There is a known issue related to Kubernetes 1.7.6 where /ui redirect does not work. Try to add trailing slash at the end of /ui redirect url: http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/

If this does not help then this means there is a problem with your cluster or you are trying to access Dashboard in a wrong way. Usually this happens when you try to expose Dashboard using kubectl proxy in a wrong way (i.e. missing permissions).

You can quickly check if accessing http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard/ instead of http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy will work for you.

Other way of checking if your issue is related to Dashboard is to expose and access it using NodePort method described in our Accessing Dashboard guide. This will allow you to access Dashboard directly without any proxy involved.

If any of described methods will work then this means it is not a Dashboard issue and you should seek for help on core repository or better yet read Kubernetes Documentation first to understand how it works.

I am using Kubernetes GCE cluster but getting forbidden access errors.

Dashboard on GCE is installed by default with very little permissions. That is not an issue. You should grant kubernetes-dashboard Service Account more privileges in order to have access to cluster resources. Read Kubernetes Documentation to find out how to do it. You can also check #2326 and #2415 (comment) for more details.

/ui redirect does not work or shows Error: 'malformed HTTP response.

Based on a way of deploying and accessing Dashboard (HTTPS or HTTP) there are different issues.

I'm accessing Dashboard over HTTP

There is a known issue related to Kubernetes 1.7.X where /ui redirect does not work. Try to add trailing slash at the end of /ui redirect url: http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/

I'm accessing Dashboard over HTTPS

The reason why /ui redirect does not work for HTTPS is that it hasn't yet been updated in the core repository. You can track https://github.com/kubernetes/kubernetes/pull/53046#discussion_r145338754 to find out when it will be merged. Probably it won't be available until K8S 1.8.3+.

Correct links that can be used to access Dashboard are in our documentation. Check Accessing Dashboard to find out more.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.