Skip to main content
This guide provides everything you need to set up Remote Execution on Astro, including prerequisites, configuration requirements, and a step-by-step checklist.

​
What you’ll configure

Remote Execution consists of both required and optional components. Understand what you need before starting setup.

​
1. Meet prerequisites

Before you begin, ensure you have:
Recommended Kubernetes configurationConfigure singleProcessOOMKill: true in your kubelet configuration. With this setting, Kubernetes kills only the process that runs out of memory instead of the entire Pod. Without it, one task’s out-of-memory error kills all tasks on the worker and loses all task logs.See Kubernetes documentation for details.
  • Helm 3 or later
  • Permissions to create Astro agents
  • A Deployment API token with Deployment Admin permissions
  • Network access from your Kubernetes cluster to Astro. Add https://<your-cluster-id>.external.astronomer.run/ to your organization’s allowlist. To find your cluster ID, go to Settings > Clusters in the Astro UI.

​
2. Required components

You must configure these components for Remote Execution to function:
  1. Register and configure agents
  2. Configure secrets backend
  3. Configure XCom backend
  4. Configure state store backend
  5. Configure Dag sources
Astronomer recommends enabling Sentinel to monitor agent health and report status to the orchestration plane. Sentinel detects Pod and component issues and monitors essential integrations such as XCom and secrets backends. See Sentinel for Remote Execution Agents.

​
4. Optional components

These components enhance functionality but aren’t required for basic operation:

​
5. Deploy your project

After you have the remote agents registered to your deployment, you can deploy your Airflow project to the Deployment.