Accessing Dashboards

Accessing Dashboards installed with KubeOps

To access a Application dashboard an SSH-Tunnel to one of the Control-Planes is needed. The following Dashboards are available and configured with the following NodePorts by default:

NodePort

30211

Initial login credentials

  • username: the username set in the kubeopsvalues.yaml for the cluster creation
  • password: the password set in the kubeopsvalues.yaml for the cluster creation

NodePort

30050

Initial login credentials

  • username: admin
  • password: admin

NodePort

  • https: 30003

Initial login credentials

  • username: admin
  • password: the password set in the kubeopsvalues.yaml for the cluster creation

NodePort

The Rook/Ceph Dashboard has no fixed NodePort yet. To find out the NodePort used by Rook/Ceph follow these steps:

  1. List the Services in the KubeOps namespace
kubectl get svc -n kubeops
  1. Find the line with the service rook-ceph-mgr-dashboard-external-http
NAME                                      TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)                                     AGE
rook-ceph-mgr-dashboard-external-http     NodePort    192.168.197.13    <none>        7000:31268/TCP                              21h

In the example above the NodePort to connect to Rook/Ceph would be 31268.

Initial login credentials

  • username: admin
  • password:
kubectl get secret rook-ceph-dashboard-password -n kubeops --template={{.data.password}} | base64 -d

The dashboard can be accessed with localhost:Port/ceph-dashboard/

NodePort

30007

Initial login credentials

An access token is required to log in to the headlamp daschboard.
The access token is linked to the service account headlamp-admin and stored in the secret headlamp-admin
The access token can be read from the secret

echo $(kubectl get secret headlamp-admin --namespace headlamp --template=\{\{.data.token\}\} | base64 --decode)

Connecting to the Dashboard

In order to connect to one of the dashboards, an ssh tunnel has to be established. There are various tools for doing this, like the command line, putty or MobaXterm.
To establish a tunnel, the NodePort of the dashboard has to be forwarded on one of the control planes to the local machine. After that the dashboard can be accessed with localhost:<Port>.

NodePort

  • https: 30003

Initial login credentials

  • username: admin
  • password: the password set in the kubeopsctl.yaml for the cluster creation

NodePort

The Rook/Ceph Dashboard has no fixed NodePort yet. To find out the NodePort used by Rook/Ceph follow these steps:

  1. List the Services in the KubeOps namespace
kubectl get svc -n kubeops
  1. Find the line with the service rook-ceph-mgr-dashboard-external-http
NAME                                      TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)                                     AGE
rook-ceph-mgr-dashboard-external-http     NodePort    192.168.197.13    <none>        7000:31268/TCP                              21h

In the example above the NodePort to connect to Rook/Ceph would be 31268.

Initial login credentials

  • username: admin
  • password:
kubectl get secret rook-ceph-dashboard-password -n kubeops --template={{.data.password}} | base64 -d

The dashboard can be accessed with localhost:Port/ceph-dashboard/#/login

NodePort

30007

Initial login credentials

An access token is required to log in to the headlamp daschboard.
The access token is linked to the service account headlamp-admin and stored in the secret headlamp-admin
The access token can be read from the secret

echo $(kubectl get secret headlamp-admin --namespace headlamp --template=\{\{.data.token\}\} | base64 --decode)

Connecting to the Dashboard

In order to connect to one of the dashboards, an ssh tunnel has to be established. There are various tools for doing this, like the command line, putty or MobaXterm.
To establish a tunnel, the NodePort of the dashboard has to be forwarded on one of the control planes to the local machine. After that the dashboard can be accessed with localhost:<Port>.