Skip to main content

Remote Execution Agent release notes

Subscribe to RSS Feed

This feature is available only if you are on the Enterprise plan or above.

The Astro Remote Execution Agent allows you to run your Airflow tasks remotely in your Kubernetes cluster, connecting to an existing Astro Deployment. This Agent provides the following components:

  • Workers: Execute tasks from specified queues
  • DAG Processor: Process and sync dags from configured sources
  • Triggerer: Handle deferrable operators and triggers

To upgrade Remote Execution Agent see Upgrade Remote Execution Agent. For general product release notes, see Astro Release Notes. If you have any questions or a bug to report, contact Astronomer support.

To see the images that are included for each release see Remote Execution Agent images.

Astro Remote Execution Agent 1.0.3​

  • Release date: July 15, 2025

Prevent airflow_local_settings.py Execution in Agent Processes​

The Remote Execution Agent process no longer imports airflow_local_settings.py. This prevents errors from user-defined settings that rely on dependencies not available in the Remote Execution Agent's isolated environment.

Images included​

See Astro Remote Execution Agent 1.0.3 images included.

Astro Remote Execution Agent 1.0.2​

  • Release date: July 3, 2025

Support for Custom Service Accounts and Annotations​

The Remote Execution Agent Helm chart now supports setting custom service account names and annotations for the Worker, Triggerer, and DAG Processor components. This allows you to:

  • Bring your own service accounts (BYO-SA) and disable the Helm-managed service account creation
  • Add annotations, such as for AWS IRSA

This update supports restricted or self-managed environments where service accounts and roles are centrally controlled.

Bug fixes​

  • Changed working directory for Remote Execution Agent images to /usr/local/airflow The workdir for Remote Execution Agent images has moved from /opt/astro to /usr/local/airflow to align with Runtime images. If you have added a manual WORKDIR /usr/local/airflow directive in your image builds you can now remove this if building from the 1.0.2 base images.
Breaking Change

If you reference /opt/astro in your Dockerfile for a Remote Execution mode Deployment, you must update those references to /usr/local/airflow.

Images included​

See Astro Remote Execution Agent 1.0.2 images included.

caution

Due to a known backwards compatibility issue in Airflow, use 3.0-1 images for Remote Deployments on Runtime 3.0-1, 3.0-2 images for Runtime 3.0-2, and 3.0-4 images for Runtime 3.0-3 and 3.0-4

Astro Remote Execution Agent 1.0.1​

  • Release date: June 2, 2025

Bug fixes​

  • Fixed a bug where the proxy rejected HEAD requests to the XCom API with a 405 Method Not Allowed. It now correctly supports HEAD requests.

Images included​

See Astro Remote Execution Agent 1.0.1 images included.

info

Use 3.0-1 images for Remote Deployments on Runtime 3.0-1, and 3.0-2 images for Runtime 3.0-2.

Astro Remote Execution Agent 1.0.0​

  • Release date: April 22, 2025

Introducing the Remote Execution Agent​

With the release of Airflow 3.0, Astro now supports Remote Execution of dags with the Astro Remote Execution Agent. The Remote Execution Agent allows you to keep your sensitive data and execute your dags in your own environment, while still leveraging Astro features like day zero Airflow Runtime support, observability, and user management. The Astro Remote Execution Agent manages running the Workers, Triggerer, and Dag Processors in your environment, while the Airflow Metadata Database, Scheduler, Web/API Server, and Remote Execution API remain in the Astro Orchestration plane.

Images included​

See Astro Remote Execution Agent 1.0.0 images included.

See Remote Execution Agents for installation, configuration, and advanced options.

Was this page helpful?