2022-09-20 10:34:42 +01:00
# Using Kubernetes
2025-04-16 16:55:51 -07:00
If you have deployed DataHub using our official [helm charts ](https://github.com/acryldata/datahub-helm ) you can use the
datahub ingestion cron subchart to schedule ingestions.
2022-09-20 10:34:42 +01:00
Here is an example of what that configuration would look like in your **values.yaml** :
```yaml
datahub-ingestion-cron:
enabled: true
crons:
mysql:
schedule: "0 * * * * " # Every hour
recipe:
configmapName: recipe-config
fileName: mysql_recipe.yml
```
This assumes the pre-existence of a Kubernetes ConfigMap which holds all recipes being scheduled in the same namespace as
where the cron jobs will be running.
An example could be:
2025-04-16 16:55:51 -07:00
2022-09-20 10:34:42 +01:00
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: recipe-config
data:
mysql_recipe.yml: |-
source:
type: mysql
config:
# Coordinates
host_port: < MYSQL HOST > :3306
database: dbname
2025-04-16 16:55:51 -07:00
2022-09-20 10:34:42 +01:00
# Credentials
username: root
password: example
2025-04-16 16:55:51 -07:00
2022-09-20 10:34:42 +01:00
sink:
type: datahub-rest
config:
server: http://< GMS_HOST > :8080
```
2025-04-16 16:55:51 -07:00
For more information, please see the [documentation ](https://github.com/acryldata/datahub-helm/tree/master/charts/datahub/subcharts/datahub-ingestion-cron ) of this sub-chart.