Airflow 3
Airflow 3 runs on each env-dataops data-platform EKS cluster through the terraform/eks-airflow-3/env/<env> roots. The dev-only test instance is managed separately at terraform/eks-airflow-3-test/env/dev.
Current Shape
| Service | Namespace | Host Pattern | Terraform Root |
|---|---|---|---|
| Airflow 3 | airflow-3 | airflow-3.data-platform.us-east-1.<env>-dataops.fetchrewards.com | terraform/eks-airflow-3/env/<env> |
| Airflow 3 Test | airflow-3-test | airflow-3-test.data-platform.us-east-1.dev-dataops.fetchrewards.com | terraform/eks-airflow-3-test/env/dev |
Airflow 3 uses a same-account ECR image repository and git-sync from git@github.com:fetch-rewards/lakehouse.git.
Git-Sync
The primary Airflow 3 roots use:
branch: mainsubpath: dags/generatedsecret: <env>/airflow-3/git-sync-ssh-keyThe dev Airflow 3 Test root uses a configurable branch and pipelines/dbt/dags/generated. This is intentionally different because it is a test deployment path.
Deployment Notes
Before merging DAG changes in the Lakehouse repository, confirm which Airflow clusters will sync the generated DAG path. The old test-dataops Airflow deployment is not managed by the new env-dataops roots.
Checked Against
terraform/eks-airflow-3/env/dev/main.tf,stage,preprod, andprodonorigin/main.terraform/eks-airflow-3-test/env/dev/main.tfonorigin/main.implementations/2026-05-21-dl-419-prod-dataops-runtime-progress.md.