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 expose
command like this:
Replace <service-name>
with:
arango-deployment-operator
for the ArangoDeployment operator dashboard.arango-storage-operator
for the ArangoLocalStorage operator dashboard. (use ‘kube-system’ namespace)
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).
This will result in something like this:
Authentication
The username+password pair is configured in a generic Kubernetes Secret
named arangodb-operator-dashboard
, found in the namespace where the operator runs.
To create such a secret, run this:
Until such a is found, the operator will respond with a status 401
to any request related to the dashboard.