Configuration & secrets

An ArangoDB cluster has lots of configuration options.Some will be supported directly in the ArangoDB Operator,others will have to specified separately.

Built-in options

All built-in options are passed to ArangoDB servers via commandlinearguments configured in the Pod-spec.

Other configuration options

All commandline options of arangod (and arangosync) are availableby adding options to the spec.<group>.args list of a groupof servers.

These arguments are added to th commandline created for these servers.

Secrets

The ArangoDB cluster needs several secrets such as JWT tokensTLS certificates and so on.

All these secrets are stored as Kubernetes Secrets and passed tothe applicable Pods as files, mapped into the Pods filesystem.

The name of the secret is specified in the custom resource.For example:

  1. apiVersion: "cluster.arangodb.com/v1alpha"
  2. kind: "Cluster"
  3. metadata:
  4.   name: "example-arangodb-cluster"
  5. spec:
  6.   mode: Cluster
  7.   auth:
  8.     jwtSecretName: <name-of-JWT-token-secret>