Configure the application database¶

AntFlow Server uses PostgreSQL to persist jobs, launcher registrations, and published-project records. Use a database reachable from the server, with credentials for the AntFlow database.

Workflow output files are stored in S3-compatible storage, not in PostgreSQL. See Store and serve workflow results to configure that storage.

Use the chart's PostgreSQL¶

The chart deploys PostgreSQL with persistent storage by default. Adjust database.persistence.storageClass and database.persistence.size for your cluster; the default requested size is 8Gi. Supply an existing PVC through database.persistence.existingClaim if its lifecycle is managed separately.

Use an existing PostgreSQL service¶

Create the database, user, and password Secret before deploying. Replace the example hostname, database, username, and Secret references with your service settings. The Secret must be in the release namespace.

database:
  enabled: false
externalDatabase:
  enabled: true
  host: postgres.example.com
  port: 5432
  database: antflow
  username: antflow
  existingSecret: antflow-database
  existingSecretPasswordKey: password

Do not enable the embedded database and external database together. Although the server also supports SQLite for standalone use, the Helm chart configures PostgreSQL; SQLite is not a chart deployment option.

Keep credentials in server-side Secrets, not in browser configuration. For database deployment options, see the Helm chart reference.