Google Git
Sign in
apache/airflow/HEAD/./chart
tree: 037d38ccbe5d65e6d59d78364863801380d09b40 [path history] [tgz]
  1. charts/
  2. dockerfiles/
  3. docs/
  4. files/
  5. newsfragments/
  6. templates/
  7. .gitignore
  8. .helmignore
  9. .pre-commit-config.yaml
  10. Chart.lock
  11. Chart.yaml
  12. INSTALL
  13. LICENSE
  14. NOTICE
  15. pyproject.toml
  16. README.md
  17. RELEASE_NOTES.rst
  18. reproducible_build.yaml
  19. values.schema.json
  20. values.yaml
  21. values_schema.schema.json
chart/README.md

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.30+ cluster
  • Helm 3.0+
  • PV provisioner support in the underlying infrastructure (optionally)

Features

  • Supported executors (all Airflow versions): LocalExecutor, CeleryExecutor, KubernetesExecutor
  • Supported executors (Airflow version 2.X.X): LocalKubernetesExecutor, CeleryKubernetesExecutor
  • 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: 1.10+, 2.0+, 3.0+
  • 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 ../docs/helm-chart

Contributing

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