Files
Rakesh PaiandPrzemysław Mirowski d3e29e1c6d Add Git-Sync to GitDagBundle migration guide for the Helm chart (#73082)
* Add migration guide from Git-Sync sidecar to GitDagBundle

The Git-Sync sidecar (dags.gitSync) is planned for removal in Helm
Chart 2.0 in favour of the Airflow-native GitDagBundle. This adds a
chart docs page mapping the old dags.gitSync values to their
dagProcessor.dagBundleConfigList equivalents, with authentication
patterns and a step-by-step migration.

* Address reviewer feedback: remove inaccurate Git-Sync claim

Veyu noted Git-Sync could checkout any commit via rev/ref params, so the statement that it always checked out the latest commit was not accurate. Removed that sentence per the preferred fix, keeping the GitDagBundle versioning note.

* docs: address review feedback on Git-Sync to GitDagBundle migration guide

- Fix spellcheck: favour -> favor (en_US)
- Generalize Git-Sync sidecar description (persistence-setting dependent)
- Prereq: latest Helm Chart 1.x release with Airflow 3
- credentialsSecret row lists both GITSYNC_* and GIT_SYNC_* key names
- Clarify what kwargs.git_conn_id refers to
- Note the Airflow Connection UI/CLI alternative to extraSecrets/extraEnv

---------

Co-authored-by: Przemysław Mirowski <17602603+Miretpl@users.noreply.github.com>
2026-11-03 19:32:05 +00:00
..
…
…

Helm Chart for Apache Airflow

Artifact HUB

Apache Airflow is a platform to programmatically author, schedule and monitor workflows.

Introduction

This chart will bootstrap an Airflow deployment on a Kubernetes cluster using the Helm package manager.

Requirements

  • Kubernetes 1.31+ cluster
  • Helm 3.0+
  • PV provisioner support in the underlying infrastructure (optionally)

Features

  • Supported executors (all Airflow versions): LocalExecutor, CeleryExecutor, KubernetesExecutor
  • Supported multiple Executors
  • Supported AWS executors with AWS provider version 8.21.0+:
    • airflow.providers.amazon.aws.executors.batch.AwsBatchExecutor
    • airflow.providers.amazon.aws.executors.ecs.AwsEcsExecutor
  • Supported Edge executor with edge3 provider version 1.0.0+:
    • airflow.providers.edge3.executors.EdgeExecutor
  • Supported Airflow version: 3.1+
  • Supported database backend: PostgreSQL, MySQL
  • Autoscaling for CeleryExecutor provided by KEDA
  • PostgreSQL and PgBouncer with a battle-tested configuration
  • Security enhancements:
    • Container-specific Service Account Token Volume configuration implementing Principle of Least Privilege
    • Only scheduler containers receive API access; init and sidecar containers operate without tokens
    • Defense-in-depth security with both ServiceAccount and Pod-level controls
    • Compatibility with security policies like Kyverno and compliance frameworks
  • Monitoring:
    • StatsD/Prometheus metrics for Airflow
    • Prometheus metrics for PgBouncer
    • Flower
  • Automatic database migration after a new deployment
  • Administrator account creation during deployment
  • Kerberos secure configuration
  • One-command deployment for any type of executor. You don't need to provide other services e.g. Redis/Database to test the Airflow.

Documentation

Full documentation for Helm Chart (latest stable release) lives on the website.

Note: If you're looking for documentation for main branch (latest development branch): you can find it on s.apache.org/airflow-docs/. Source code for documentation is in chart/docs

Contributing

Want to help build Apache Airflow? Check out our contributing documentation.