A Helm chart for deploying Flowker - Workflow orchestration platform for financial validation.
helm install flowker ./charts/flowker -n flowker --create-namespace
By default, resources are deployed to the flowker namespace. Override with:
helm install flowker ./charts/flowker --set namespaceOverride=custom-namespace -n custom-namespace
The chart includes a MongoDB subchart (Bitnami) enabled by default. To use an external MongoDB instance, disable the bundled one:
mongodb:
enabled: false
flowker:
configmap:
MONGO_URI: "mongodb://user:password@your-mongo-host:27017/flowker?authSource=admin"
To use an existing Kubernetes secret instead of the chart-managed one:
flowker:
useExistingSecret: true
existingSecretName: "my-flowker-secret"
The secret must contain the keys defined in flowker.secrets (e.g., MONGO_APP_PASSWORD, API_KEY).
| Parameter | Description | Default |
|---|---|---|
namespaceOverride |
Override the namespace for all resources | flowker |
flowker.enabled |
Enable flowker deployment | true |
flowker.replicaCount |
Number of replicas | 1 |
flowker.image.repository |
Image repository | ghcr.io/lerianstudio/flowker |
flowker.image.tag |
Image tag | 1.0.0-beta.22 |
flowker.service.port |
Service port | 4000 |
flowker.ingress.enabled |
Enable ingress | false |
flowker.autoscaling.enabled |
Enable HPA | true |
flowker.pdb.enabled |
Enable PodDisruptionBudget | true |
flowker.useExistingSecret |
Use an existing secret | false |
flowker.existingSecretName |
Name of the existing secret | "" |
mongodb.enabled |
Enable bundled MongoDB subchart | true |
For full configuration options, see values.yaml.