Using the ArangoDB Kubernetes Operator with Helm

    The benefit of helm (in the context of the ArangoDB Kubernetes Operator)is that it allows for a lot of flexibility in how you install the operator.For example you can install the operator in a namespace other thandefault.

    The ArangoDB Kubernetes Operator is contained in two helm charts:

    • kube-arangodb which contains the operator for the ArangoDeploymentand ArangoDeploymentReplication resource types.
    • kube-arangodb-storage which contains the operator for the ArangoLocalStorageresource type.The kube-arangodb-storage only has to be installed if your Kubernetes clusterdoes not already provide StorageClasses that use locally attached SSDs.

    Values are passed to helm using an —set=<key>=<value> argument passedto the helm install or helm upgrade command.

    The kube-arangodb chart supports deployment into a non-default namespace.

    Note that since the operators claim exclusive access to a namespace, you caninstall the kube-arangodb chart in a namespace once.You can install the kube-arangodb chart in multiple namespaces. To do so, run:

    1. helm install --namespace=namespace1 kube-arangodb.tgz

    The kube-arangodb-storage chart is always installed in the kube-system namespace.

    For various ways to work around this problem go to this Stackoverflow article.