arango-platform-release

Arango Platform Release 4.1.0.

This chart installs an Arango Platform release onto an existing ArangoDeployment. It bundles 26 platform chart(s) and 10 service(s), which are created as ArangoPlatformChart and ArangoPlatformService resources and reconciled by the ArangoDB operator.

This file is generated when the release chart is packaged. Do not edit it by hand.

Installation

The name of the target ArangoDeployment is required:

helm install <release-name> <chart> \
  --namespace <namespace> \
  --set deployment=<arango-deployment-name>

Container Images

This release uses the container images below, aggregated from the bundled charts. For an air-gapped installation, pull each image, re-tag it to your private registry, push it, and override it at the listed values path.

The same list is available as a machine-readable images.yaml at the root of this chart. To mirror every image to my.registry.example.com:

for img in \
  registry.license.arango.ai/arango-control-plane/service:v0.0.23 \
  registry.license.arango.ai/arango-cypher2aql/service:v0.9.8 \
  registry.license.arango.ai/arango-mcp-server-advanced/service:v0.0.12 \
  registry.license.arango.ai/arango-user-defined/node22base:v0.0.7 \
  registry.license.arango.ai/arango-user-defined/py12base:v0.0.7 \
  registry.license.arango.ai/arango-user-defined/py12cugraph:v0.0.7 \
  registry.license.arango.ai/arango-user-defined/py12torch:v0.0.7 \
  registry.license.arango.ai/arangodb-mlflow/service:v0.1.10 \
  registry.license.arango.ai/autograph/opentelemetry-collector-contrib:v0.0.16 \
  registry.license.arango.ai/autograph/service:v0.0.16 \
  registry.license.arango.ai/featurization/job-cpu:v1.0.13 \
  registry.license.arango.ai/file-manager/opentelemetry-collector-contrib:v0.0.22 \
  registry.license.arango.ai/file-manager/service:v0.0.22 \
  registry.license.arango.ai/file-parser/service-api:v0.1.3 \
  registry.license.arango.ai/file-parser/service-orchestrator:v0.1.3 \
  registry.license.arango.ai/file-parser/service-worker-default:v0.1.3 \
  registry.license.arango.ai/file-parser/service-worker-pdf:v0.1.3 \
  registry.license.arango.ai/gral/engine:v1.1.13 \
  registry.license.arango.ai/graph-rag/service:v0.0.17 \
  registry.license.arango.ai/graphrag-importer/opentelemetry-collector-contrib:v0.0.34 \
  registry.license.arango.ai/graphrag-importer/service:v0.0.34 \
  registry.license.arango.ai/graphrag-retriever/opentelemetry-collector-contrib:v0.0.20 \
  registry.license.arango.ai/graphrag-retriever/service:v0.0.20 \
  registry.license.arango.ai/llm-host/service:v0.0.19 \
  registry.license.arango.ai/ml-api/service:v1.0.16 \
  registry.license.arango.ai/notebook-images/service:v0.5.56 \
  registry.license.arango.ai/platform-monitoring/grafana:v0.0.8 \
  registry.license.arango.ai/platform-monitoring/prometheus-config-reloader:v0.0.8 \
  registry.license.arango.ai/platform-monitoring/prometheus:v0.0.8 \
  registry.license.arango.ai/platform-ui/core-ui:v1.5.0 \
  registry.license.arango.ai/platform-ui/server:v1.5.1 \
  registry.license.arango.ai/platform-ui/ui:v1.5.1 \
  registry.license.arango.ai/prediction/job-cpu:v1.0.15 \
  registry.license.arango.ai/prediction/job-gpu:v1.0.15 \
  registry.license.arango.ai/reasoner/service:v0.0.10 \
  registry.license.arango.ai/training/job-cpu:v1.0.12 \
  registry.license.arango.ai/training/job-gpu:v1.0.12 \
  ; do
  docker pull "$img"
  docker tag "$img" "my.registry.example.com/${img#*/}"
  docker push "my.registry.example.com/${img#*/}"
done

Values

Overrides are merged on top of the values each chart was packaged with, so only the keys you want to change need to be listed. Unknown chart or service names are rejected by values.schema.json.

A complete values.yaml for this release, with every override block left empty:

deployment: my-deployment
charts:
  arango-control-plane: {}
  arango-cypher2aql: {}
  arango-user-defined: {}
  arangodb-autograph: {}
  arangodb-core-ui: {}
  arangodb-featurization-cpu: {}
  arangodb-file-parser: {}
  arangodb-gral: {}
  arangodb-graph-rag: {}
  arangodb-graphrag-importer: {}
  arangodb-graphrag-retriever: {}
  arangodb-llm-host: {}
  arangodb-mcp-server: {}
  arangodb-ml-api: {}
  arangodb-mlflow: {}
  arangodb-notebook-images: {}
  arangodb-platform-ui: {}
  arangodb-platform-ui-server: {}
  arangodb-prediction-cpu: {}
  arangodb-prediction-gpu: {}
  arangodb-reasoner: {}
  arangodb-training-cpu: {}
  arangodb-training-gpu: {}
  file-manager: {}
  platform-monitoring-grafana: {}
  platform-monitoring-prometheus: {}
services:
  arango-control-plane:
    values: {}
  arangodb-core-ui:
    values: {}
  arangodb-file-parser:
    values: {}
  arangodb-ml-api:
    values: {}
  arangodb-mlflow:
    values: {}
  arangodb-platform-ui:
    values: {}
  arangodb-platform-ui-server:
    values: {}
  file-manager:
    values: {}
  platform-monitoring-grafana:
    values: {}
  platform-monitoring-prometheus:
    values: {}

Bundled charts

Charts that ship a values.schema.json have their override block validated against it, with required constraints relaxed because overrides are a partial document. Charts without a schema accept any values.

Chart values

Every value each chart exposes, with the default it is packaged with. Values are listed by their full path, so charts.<chart>.images.application.tag is set as:

charts:
  <chart>:
    images:
      application:
        tag: <value>

or on the command line:

--set charts.<chart>.images.application.tag=<value>

The same values can be set per service under services.<service>.values - see Services. Descriptions are taken from the chart's values.schema.json where it provides them.

arango-control-plane

arango-cypher2aql

arango-user-defined

arangodb-autograph

arangodb-core-ui

arangodb-featurization-cpu

arangodb-file-parser

arangodb-gral

arangodb-graph-rag

arangodb-graphrag-importer

arangodb-graphrag-retriever

arangodb-llm-host

arangodb-mcp-server

arangodb-ml-api

arangodb-mlflow

arangodb-notebook-images

arangodb-platform-ui

arangodb-platform-ui-server

arangodb-prediction-cpu

arangodb-prediction-gpu

arangodb-reasoner

arangodb-training-cpu

arangodb-training-gpu

file-manager

platform-monitoring-grafana

platform-monitoring-prometheus

Services

Each service accepts the same values as the chart it is created from, set under services.<service>.values instead of charts.<chart>. See Chart values for the full list, for example:

services:
  arango-control-plane:
    values: {}
  arangodb-core-ui:
    values: {}
  arangodb-file-parser:
    values: {}
  arangodb-ml-api:
    values: {}
  arangodb-mlflow:
    values: {}
  arangodb-platform-ui:
    values: {}
  arangodb-platform-ui-server:
    values: {}
  file-manager:
    values: {}
  platform-monitoring-grafana:
    values: {}
  platform-monitoring-prometheus:
    values: {}

Verifying the installation

kubectl get arangoplatformcharts -n <namespace>
kubectl get arangoplatformservices -n <namespace>

Both resources report a Ready condition once the operator has reconciled them.