Apache Airflow feature support

Apache Airflow releases features at varying levels of maturity. Some features ship as experimental in Airflow itself, and a small set of upstream features aren’t supported on Astro. This document explains how Astronomer supports experimental Airflow features and lists the upstream Airflow features that Astro doesn’t support.

For the lifecycle policy that applies to Astronomer-released products and features, see Astronomer feature lifecycle.

Experimental Airflow features

Apache Airflow marks some features as experimental. These features ship in Airflow releases, but their interfaces, behaviors, and stability characteristics can change between versions without notice.

Astronomer provides best-effort support for experimental Airflow features on Astro. Best-effort support means that Astronomer support investigates issues and helps you find workarounds where possible. SLAs don’t apply to experimental features, and some issues require an upstream fix in Apache Airflow before Astronomer can resolve them.

Unsupported Airflow features

The following upstream Apache Airflow features aren’t supported on Astro:

• Edge executor: The Apache Airflow Edge executor isn’t supported on Astro. For distributed task execution outside the Astro data plane, use Remote Execution Agents.
• Airflow multi-team: The Airflow 3 multi-team model isn’t supported on Astro. Astro provides tenant isolation through Organizations, Workspaces, and Deployments. See About Astro.
• Auth managers: Apache Airflow auth managers aren’t supported on Astro. This includes the simple auth manager, the FAB auth manager, and any custom or third-party auth managers. Astro uses its own authentication and authorization system. See Organization users and Set up SSO.

If you have questions about a specific Airflow feature, submit a support request.