Accessing Dashboards installed with KubeOps
4 minute read
To access an 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:
enterprise-values.yaml.
See Fileformats for details.
NodePort
32090 (if not set otherwise in the enterprise-values.yaml)
Connecting via SSH Tunnel
To establish a tunnel, forward the NodePort from one of the control planes to your local machine. You can use the command line, PuTTY, or MobaXterm for this.
After that, the dashboard can be accessed at localhost:32090/prometheus/.
Connecting via Ingress
The dashboard can also be accessed via https://<your-domain>/prometheus/.
Initial login credentials
No credentials are necessary for login.
NodePort
30211 (if not set otherwise in the enterprise-values.yaml)
Connecting via SSH Tunnel
To establish a tunnel, forward the NodePort from one of the control planes to your local machine. You can use the command line, PuTTY, or MobaXterm for this.
After that, the dashboard can be accessed at localhost:30211/grafana/.
Connecting via Ingress
The dashboard can also be accessed via https://<your-domain>/grafana/.
Initial login credentials
- username: the username set in the enterprise-values.yaml of Prometheus (default: user)
- password: the password set in the enterprise-values.yaml of Prometheus (default: password)
NodePort
30050 (if not set otherwise in the enterprise-values.yaml)
Connecting via SSH Tunnel
To establish a tunnel, forward the NodePort from one of the control planes to your local machine. You can use the command line, PuTTY, or MobaXterm for this.
After that, the dashboard can be accessed at localhost:30050/.
Connecting via Ingress
The dashboard can also be accessed via https://<your-domain>/opensearch/.
Login
OpenSearch Dashboards supports Single Sign-On (SSO) via Keycloak as the primary login, with username/password as a fallback.
- SSO (recommended): open
https://<your-domain>/opensearch/and choose Log in with single sign-on. You are redirected to Keycloak. See the SSO for OpenSearch guide for setup and how to grant users access. - Username / password (fallback):
- username:
admin - password: the value of
adminPasswordin the enterprise-values.yaml (default:Password@@123456)
- username:
SSO is only wired up when the OpenSearch hostname points to a reachable Keycloak
(non-.local). For *.local hostnames only the username/password login is available.
See Changing the OpenSearch password to change admin.
NodePort
- HTTP: 30002
- HTTPS: 30003
Connecting via SSH Tunnel
To establish a tunnel, forward port 30002 from one of the control planes to your local machine. You can use the command line, PuTTY, or MobaXterm for this.
After that, the dashboard can be accessed at localhost:30002/.
Connecting via Ingress
The dashboard can also be accessed via https://<your-domain>/.
Initial login credentials
- username: admin
- password: the password set in the enterprise-values.yaml (default: password)
NodePort
The Rook/Ceph dashboard has no fixed NodePort. To find the NodePort in use, run one of the following:
kubectl get svc -n rook-ceph
Look for the rook-ceph-mgr-dashboard-external-http service:
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
Or retrieve the NodePort directly:
echo $(kubectl get -n rook-ceph -o jsonpath="{.spec.ports[0].nodePort}" services rook-ceph-mgr-dashboard-external-http)
In the example above, the NodePort is 31268.
Connecting via SSH Tunnel
To establish a tunnel, forward the NodePort from one of the control planes to your local machine. You can use the command line, PuTTY, or MobaXterm for this.
After that, the dashboard can be accessed at localhost:<NodePort>/ceph-dashboard/.
Connecting via Ingress
The dashboard can also be accessed via https://<your-domain>/ceph-dashboard/.
Initial login credentials
echo Username: admin
echo Password: $(kubectl get secret rook-ceph-dashboard-password -n rook-ceph --template={{.data.password}} | base64 -d)
NodePort
30007 (if not set otherwise in the enterprise-values.yaml)
Connecting via SSH Tunnel
To establish a tunnel, forward the NodePort from one of the control planes to your local machine. You can use the command line, PuTTY, or MobaXterm for this.
After that, the dashboard can be accessed at localhost:30007/kubeops-dashboard/.
Connecting via Ingress
The dashboard can also be accessed via https://<your-domain>/kubeops-dashboard/.
Initial login credentials
kubectl -n monitoring create token headlamp-admin
NodePort
30180
Connecting via SSH Tunnel
To establish a tunnel, forward the NodePort from one of the control planes to your local machine. You can use the command line, PuTTY, or MobaXterm for this.
After that, the dashboard can be accessed at localhost:30180/keycloak/.
Connecting via Ingress
The dashboard can also be accessed via https://<your-domain>/keycloak/.
Initial login credentials
echo Username: $(kubectl get secret --namespace keycloak keycloak-kubeops -o jsonpath="{.data.ADMIN_USER}" | base64 -d)
echo Password: $(kubectl get secret --namespace keycloak keycloak-kubeops -o jsonpath="{.data.ADMIN_PASSWORD}" | base64 -d)