Skip to content

Decouple Task SDK & Airflow Core for server/client separation #51553

Closed
4 of 4 issues completed
Closed

Description

@kaxil

Follow-up of https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-72+Task+Execution+Interface+aka+Task+SDK work for Airflow 3.1

Overview

Implement AIP-72 server-client separation to decouple Airflow's orchestration server from task execution components.

Goals

  • Enable independent deployment of server and workers
  • Support future multi-language SDKs (Go, etc.)
  • Remove circular dependencies between core and task-sdk & decouple them

Approach

  1. Investigate shared components - Determine what needs common packages
  2. Break core dependencies - Remove task-sdk imports from airflow-core
  3. Resolve component placement - Decide where Triggerer, DAG Processor, etc. live
  4. Update ecosystem - Migrate provider packages to new architecture

Activity

  1. converted this from a draft issue on Jun 9, 2025
  2. added this to the Airflow 3.1.0 milestone on Jun 9, 2025
  3. moved this from Next 2 Weeks to In Progress in AIP-72 - Task Execution Interface and SDKon Jun 18, 2025
  4. moved this from In Progress to Next 2 Weeks in AIP-72 - Task Execution Interface and SDKon Jun 24, 2025
  5. moved this from Next 2 Weeks to In Progress in AIP-72 - Task Execution Interface and SDKon Feb 17, 2026
  6. amoghrajesh commented on Feb 17, 2026

    @amoghrajesh
    Contributor

    Work items under this epic have been handled for Airflow 3.1/3.2, remaining issues out of scope for Airflow 3.2 are tracked here: #62061

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions