Operator Dashboards

The dashboards do not provide direct means to modify the resources.All modifications are done using 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) operatora Service is created that serves the dashboard internally in the Kubernetes cluster.To expose a dashboard outside the Kubernetes cluster, run a kubecty exposecommand like this:

• arango-deployment-operator for the ArangoDeployment operator dashboard.
• arango-storage-operator for the ArangoLocalStorage operator dashboard. (use ‘kube-system’ namespace)Replace <the-namespace> with the name of the namespace that the operator is in.This will often be default.

This will create an additional Service of type that copiesthe selector from the existing Service.If your Kubernetes cluster does not support loadbalancers,use —type=NodePort instead.

Run the following command to inspect your new service and look for theloadbalancer IP/host address (or nodeport).

Authentication

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 Secret named arangodb-operator-dashboard, found in the namespace where the operator runs.

Until such a is found, the operator will respond with a status 401to any request related to the dashboard.