Skip to content

Conversation

@Simran-B
Copy link
Contributor

@Simran-B Simran-B commented Dec 2, 2025

Description

Open tasks and questions:

  • Are there any new metrics or changes not yet mentioned, e.g. regarding the shorter expiration of licenses, like the web UI?
  • Do we already support a custom registry to pull the Data Platform images from instead of using a zipped platform package?
  • For Starter deployments, should we recommend not using -e ARANGO_LICENSE_KEY unless for e.g. air-gapped environments and link to the license management page for how to activate a deployment using the Platform CLI tool?
  • Do we issue licenses that are valid for more than 2 weeks for customers with air-gapped environments?

Upstream PRs

  • 3.10:
  • 3.11:
  • 3.12:
  • 4.0:

Note

Documents the new deployment ID API, overhauls Enterprise license management (activation/keys), updates 3.12 release notes, and adds/expands Arango Data Platform installation docs.

  • HTTP API (Administration)
    • Add GET /_admin/deployment/id endpoint (3.12 & 4.0) with schema and curl example.
  • License Management Docs
    • Overhaul to introduce activation via license credentials and key generation flow; clarify applying a "license key"; cross-link updates in JS API (db._setLicense).
  • Release Notes (3.12)
    • Note new Deployment ID endpoint and license management changes (short‑lived activations/keys) in API changes, incompatible changes, and what's new (mirrored in 4.0 docs).
  • Data Platform Docs
    • Expand overview, add deployment options; add new "Installation" guide; simplify "Get Started"; update release notes and add alias.

Written by Cursor Bugbot for commit 559dd84. This will update automatically on new commits. Configure here.

@Simran-B Simran-B added this to the 3.12.6 milestone Dec 2, 2025
@Simran-B Simran-B requested review from ajanikow and nerpaula December 2, 2025 09:41
@arangodb-docs-automation
Copy link
Contributor

Deploy Preview Available Via
https://deploy-preview-843--docs-hugo.netlify.app

@cla-bot cla-bot bot added the cla-signed label Dec 2, 2025
@Simran-B Simran-B self-assigned this Dec 2, 2025
@Simran-B Simran-B requested a review from maxkernbach December 18, 2025 14:20
Copy link
Contributor

@maxkernbach maxkernbach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Simran-B Overall this looks good to me.

My feedback is mainly regarding the platform installation section, which I was able to test. I have added a few comments for your consideration.


```sh
# User credentials
curl -uroot: http://localhost:8529/_admin/deployment/id
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor typo:

Suggested change
curl -uroot: http://localhost:8529/_admin/deployment/id
curl -u root: http://localhost:8529/_admin/deployment/id

Comment on lines +214 to +234
```yaml
apiVersion: "database.arangodb.com/v1"
kind: "ArangoDeployment"
metadata:
name: "deployment-example"
spec:
mode: Cluster
image: "arangodb/enterprise:3.12.7"
gateway:
enabled: true
dynamic: true
gateways:
count: 1
dbservers:
count: 3
coordinators:
count: 2
license:
secretName: arango-license-key
# ...
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sample Arangodeployment does not mention the vector index option, which is quite important when running GraphRAG. I'm not sure whether vector indexes are enabled by default in 3.12.7 (no default is displayed in the vector index documentation)?

package configuration file.

```sh
arangodb_operator_platform --context arangodb package install \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm unsure whether --context arangodb is supported? I have always been using -n arangodb \.

arangodb_operator_platform --context arangodb package install \
--license.client.id "<license-client-id>" \
--license.client.secret "<license-client-secret>" \
--platform.name deployment-example \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Clarify that deployment-example refers to the name of the Arangodeployment.


### Step 9: Set up object storage

Features like GraphML require an additional storage system to save model
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Features like GraphML require an additional storage system to save model
Features like MLflow or GraphML require an additional storage system to save model

mountPath: /data
volumes:
- name: data
emptyDir: {}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I setup the minio service locally, I wasn't able to successfully upload any file to minio using emptyDir. Instead, I had to create a PersitentVolumeClaim in addition, and configured the volumes section as follows:

      volumes:
        - name: data
          persistentVolumeClaim:
            claimName: minio-data-pvc

minio-pvc.yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
 name: minio-data-pvc
 namespace: minio
spec:
 accessModes:
   - ReadWriteOnce
 resources:
   requests:
     storage: 5Gi

Comment on lines +433 to +442
## Interfaces

The Arango Data Platform uses a gateway to make all its services available via a
single port at the external address of the deployment. For a local deployment,
the base URL is `https://127.0.0.1:8529`.

### Unified web interface

You can access the Arango Data Platform web interface with a browser by appending
`/ui/` to the base URL, e.g. `https://127.0.0.1:8529/ui/`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even if the Data Platform is deployed in a local environment, we need to port-forward to the gateway pod in order to access the UI. I would suggest to add the kubectl command to enable the port-forwarding. Usually I'm performing the port-forwarding via k9s (not sure if we want to mention k9s as an optional tool to monitor our platform?).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any issues with this documentation. But at the same time I have not validated these steps myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants