<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->

Helm Chart for Apache Airflow

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.11.X): LocalKubernetesExecutor, CeleryKubernetesExecutor
• Supported multiple Executors (2.11+)
• 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: 2.11+, 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.