ArangoDB v3.12 is under development and not released yet. This documentation is not final and potentially incomplete.
The ArangoDB Kubernetes Operator can create a dashboard for each type of resource it supports. These dashboards are intended to give an overview of the created resources, their state and instructions on how to modify those resources.
The dashboards do not provide direct means to modify the resources.
All modifications are done using
kubectl commands (which are provided by the dashboards)
so the standard security of your Kubernetes cluster is not bypassed.
For each resource type (deployment, deployment replication & local storage) operator
Service is created that serves the dashboard internally in the Kubernetes cluster.
To expose a dashboard outside the Kubernetes cluster, run a
command like this:
kubectl expose service <service-name> --type=LoadBalancer \ --port=8528 --target-port=8528 \ --name=<your-exposed-service-name> --namespace=<the-namespace>
arango-deployment-operatorfor the ArangoDeployment operator dashboard.
arango-deployment-replication-operatorfor the ArangoDeploymentReplication operator dashboard.
arango-storage-operatorfor the ArangoLocalStorage operator dashboard. (use ‘kube-system’ namespace)
<the-namespace> with the name of the namespace that the operator is in.
This will often be
This will create an additional
Service of type
LoadBalancer that copies
the selector from the existing
If your Kubernetes cluster does not support loadbalancers,
Run the following command to inspect your new service and look for the loadbalancer IP/host address (or nodeport).
kubectl get service <your-exposed-service-name> --namespace=<the-namespace>
This will result in something like this:
$ kubectl get service arango-storage-operator-lb --namespace=kube-system NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE arango-storage-operator-lb LoadBalancer 10.103.30.24 192.168.31.11 8528:30655/TCP 1d
While the dashboards do not provide any means to directly modify resources, they still show sensitive information (e.g. TLS certificates). Therefore the dashboards require a username+password for authentications.
The username+password pair is configured in a generic Kubernetes
arangodb-operator-dashboard, found in the namespace where the operator runs.
To create such a secret, run this:
kubectl create secret generic \ arangodb-operator-dashboard --namespace=<the-namespace> \ --from-literal=username=<username> \ --from-literal=password=<password>
Until such a
Secret is found, the operator will respond with a status
to any request related to the dashboard.