Skip to content
ArtificialFlow

Deployment

Two paths, one topology. Compose is a single host. Helm is Kubernetes. Both run Postgres, Elasticsearch, Kafka, Debezium, and the ArtificialFlow services.

PathFileUse
Docker Composedocker-compose.ymlLocal development, evaluation, one machine
Helmcharts/artificialflowKubernetes and production

ArtificialFlow does not ship an identity product. IAM_DEPLOYMENT_MODE (Helm iam.mode) is a boolean. true is the Helm default and uses your OIDC provider. false is the Compose default: console admin / admin, and the API needs no token. external and disabled fail startup. --set-string iam.mode=false also fails, because the chart requires a real YAML boolean.

Images

Five images: artificialflow/workflow-command, workflow-runtime, workflow-query, sync-worker, and frontend. They run as UID and GID 10001. The same digests are also pushed under the deprecated azizaltaleb namespace. New installs use artificialflow/*.

A release publishes v1.2.0, 1.2.0, and 1.2. Compose and the chart pin 1.2.0. There is no latest tag. That pin is not on Docker Hub yet. The images built from commit 6b80b6b are published as candidate-v1.2.0-6b80b6b7700bab43f6fe0d8c35ec062b341b90ed.

Third-party images in the stack: postgres:15-alpine, Elasticsearch 8.11.1, confluentinc/cp-kafka:7.6.1, debezium/connect:2.6, and nginx:alpine for the Compose gateway.

Docker Compose

make up builds from the checkout. make up-release pulls images and starts them with --no-build. It does not use a Compose override file.

git clone --depth 1 --branch release/v1.2.0 https://github.com/artificialflow/artificialflow.git
cd artificialflow
make smoke
make up
# or, once tag 1.2.0 is published:
ARTIFICIALFLOW_IMAGE_TAG=1.2.0 make up-release

make smoke renders docker-compose.yml and checks the Kafka wiring without starting containers. Schema migration runs when command and runtime open Postgres. The sync worker registers the Debezium connector. make init-connector is a recovery action only. make down stops the stack. make clean also deletes artificialflow-postgres-data and artificialflow-elasticsearch-data.

The deploy builder writes one Compose file with the gateway config embedded, so you can start it without the rest of the repository.

Helm

No Helm repository is published. Install the chart from a clone of release/v1.2.0. Chart version and appVersion are 1.2.0.

git clone --depth 1 --branch release/v1.2.0 https://github.com/artificialflow/artificialflow.git
cd artificialflow
helm upgrade --install artificialflow ./charts/artificialflow \
  --namespace artificialflow --create-namespace \
  -f my-values.yaml

A small values file for an OIDC install:

iam:
  mode: true
  auth:
    issuerInternalUrl: https://login.example.com
    issuerPublicUrl: https://login.example.com
    clientId: workflow-backend
  frontend:
    oidcClientId: workflow-frontend
ingress:
  host: app.example.com
cors:
  allowedOrigins: https://app.example.com
postgresql:
  password: replace-me

Postgres, Elasticsearch, Kafka, and Debezium are bundled unless you set bundled.enabled: false and give an address. values-kind-smoke.yaml sets iam.mode: false for a cluster smoke test. values-production-reference.yaml is the HA shape, including three multi-active runtimes. make validate-helm renders the supported combinations.

There is no migration Job. Command and runtime apply pending migrations under a Postgres advisory lock before they serve. The startup probe window is 10 minutes by default (5s × 120). App Deployments roll with maxUnavailable: 0. Values under the old migration.* key fail rendering. Remove them.

To register Debezium yourself, set syncWorker.env.CONNECT_BOOTSTRAP_ENABLED: "false". The deploy builder does that when you point the chart at managed services. Fresh installs leave compatibility.legacyResourceNames off.

Ready means every pod is Ready, /api/identity/me shows the expected roles when IAM is on, the connector tasks are RUNNING, and a deployed workflow appears in the query API. /health only proves the process is up.