kube-arangodb

kube-arangodb

Chainguard's redistribution of the kube-arangodb Helm chart, pre-configured with hardened Chainguard Images.

The chart deploys the ArangoDB Kubernetes Operator, which manages ArangoDB deployments through custom resources such as ArangoDeployment, ArangoDeploymentReplication, ArangoBackup, ArangoBackupPolicy, ArangoMember, and ArangoLocalStorage.

Prerequisites

Authentication is required to access this chart and its images. First, authenticate with Chainguard and configure your environment:

chainctl auth login
chainctl auth configure-docker --pull-token --save
helm registry login cgr.dev

Create an image pull secret for the cluster:

kubectl create secret docker-registry cgr-pull-secret \
  --docker-server=cgr.dev \
  --docker-username="$(echo cgr.dev | docker-credential-cgr get | jq -r '.Username')" \
  --docker-password="$(echo cgr.dev | docker-credential-cgr get | jq -r '.Secret')"

Installation

helm install kube-arangodb oci://cgr.dev/ORGANIZATION/charts/kube-arangodb \
  --set operator.imagePullSecrets[0]=cgr-pull-secret

The upstream chart lists operator.imagePullSecrets as plain secret names, not name objects.

By default the chart schedules the operator only on amd64 nodes through operator.architectures. To run on arm64 nodes, override the list, for example --set 'operator.architectures={amd64,arm64}'.

About This Chart

This is a redistribution of the upstream kube-arangodb Helm chart. All upstream configuration options and documentation apply.

For full documentation, see: https://arangodb.github.io/kube-arangodb/