ArangoDB Platform Releases

Helm charts for ArangoDB Platform (AI Suite) releases. Each release is a single self-contained umbrella chart with every platform chart embedded, so installing it needs no access to the ArangoDB chart registry.

Releases

VersionChartManifestDocsContents
4.1.0 arango-platform-release-v4.1.0.tgz Release.yaml Documentation 26 charts, 10 services
4.0.2 arango-platform-release-v4.0.2.tgz Release.yaml Documentation 23 charts, 7 services
4.0.1 arango-platform-release-v4.0.1.tgz Release.yaml Documentation 23 charts, 7 services

Aliases

AliasPoints atChart
plg 4.1.0 arango-platform-release.tgz

An alias is a stable path for an environment, so the URL does not change when that environment moves to a new release. An alias serves the documentation and chart of the release it points at directly — there is no redirect — and is updated by hand.

Installing

Download the chart for the release you want from the table above, then install it onto an existing ArangoDeployment:

helm install my-platform ./arango-platform-release-v4.1.0.tgz \
  --namespace <namespace> \
  --set deployment=<arango-deployment-name>

deployment is required — it names the ArangoDeployment the release is installed onto. Installing creates one ArangoPlatformChart per bundled chart and one ArangoPlatformService per service, which the ArangoDB operator reconciles.

Upgrading to a later release is a normal Helm upgrade against that release's chart:

helm upgrade my-platform ./arango-platform-release-v4.1.0.tgz \
  --namespace <namespace> \
  --reuse-values

Configuration

Each release has its own documentation page, linked in the table above, covering every bundled chart and service together with its configurable values — start there when you need to override something. Overrides are supplied per chart and per service:

helm install my-platform ./arango-platform-release-v4.1.0.tgz \
  --namespace <namespace> \
  --set deployment=<arango-deployment-name> \
  --values overrides.yaml

The chart ships a values.schema.json, so unknown keys and malformed overrides are rejected at install time rather than producing a broken deployment.

Helm repository index

index.yaml is a Helm repository index covering every release listed above, kept up to date as releases are added. Because this site is access-controlled, the Helm CLI cannot authenticate against it — helm repo add receives a login page rather than the index. Install from the downloaded chart file instead, as shown above.