Changes / Orchestration / Apache Airflow
End of supporthigh impact
Apache Airflow 2 reached end of life on April 22, 2026
Airflow 2 moves to limited maintenance on Oct 22, 2025 and is EOL on Apr 22, 2026, after which it gets no fixes or support.
Who’s affected
Any team still running self-managed Apache Airflow 2.x (2.11.2 was the last patch). Managed services that still run 2.x are affected too, depending on the vendor's own support policy.
Not affected: Teams already on Airflow 3 and teams whose managed provider has already moved them off 2.x.
What it costs
No license price changed, but Airflow 2 has been past end of life since April 22, 2026, so it gets no fixes or support. The cost is migration effort: DAG and provider compatibility testing, plus staging and rollout time, with security exposure growing the longer you wait.
When to act
The EOL date has already passed, and a typical Airflow major-version migration needs 4-6 months of inventory, testing and cutover, so start immediately.
Blast radius: Airflow upgrades can break custom operators, plugins, provider packages, auth/RBAC config, DAG imports, scheduled dbt runs and downstream SLAs, and CI/CD or deployment tooling tied to 2.x.
What should you do? decision tree
- you are already on Airflow 3 or a managed service that has upgraded youConfirm the version in production, then close this item.
- you run Airflow 2.x and have not started a migration planInventory DAGs, custom operators, plugins, providers and auth setup, and build a staging environment on Airflow 3 this month.
- your DAGs rely on deprecated APIs or heavy custom plugins that are costly to portEvaluate whether to port to Airflow 3 or move those workloads to another orchestrator.
- you use a managed Airflow vendor still offering 2.xAsk for their written support end date and upgrade path for 2.x, and plan around it.
- you cannot migrate soonFreeze changes, isolate the instance from the public internet, tighten access and monitoring, and set a firm migration date as a stopgap.
Options
- WaitStay on 2.11.2 with network isolation and tight access controls. Only a short stopgap, since no fixes or support are coming.
- OptimizeClean up unused DAGs, pin provider versions and remove deprecated APIs now to shrink the migration scope.
- UpgradeMove to the current Airflow 3 release in staging, run DAG parse and integration tests, then cut over in waves.
- MigrateMove to a managed Airflow service or another orchestrator if you lack platform engineering capacity to run upgrades yourself.
Alternatives editorial picks, not sponsored
The facts straight from the source
Facts above are extracted from the source and checked word-for-word before publishing. The guidance sections are AI-assisted analysis based only on those facts: a starting point, not legal or procurement advice. Spotted an error? Tell us.