API server autoscaling is generally available
API server autoscaling for Airflow 3 deployments is now generally available. It automatically adjusts replicas based on CPU utilization.
36 releases · 3 this month
API server autoscaling for Airflow 3 deployments is now generally available. It automatically adjusts replicas based on CPU utilization.
Astronomer Astro now supports executing GPU workloads on AWS by requesting NVIDIA GPU node pool resources within KubernetesPodOperator tasks.
Each bundle on a Deployment now records a version history, and you can roll one bundle back to a version in that history. Your project image, your Astro Runtime version, and every other bundle stay as they are. Previously, the only way to undo a change to one bundle was to roll back the whole Deployment.
The Astro UI now provides a progress card and dedicated logs for Airflow database migrations during runtime upgrades.
Users can now create AWS dedicated clusters in the eu-west-3 (Paris) region.
Deployment hibernation is now generally available on Astro, allowing users to scale development deployment resources to zero on a schedule or on demand.
Astro now stores XCom and task state values larger than 64 KB in an Astro-managed object storage bucket instead of the Airflow metadata database for improved performance.
- You can now turn on Development Mode for an existing Deployment from the Deployment settings in the Astro UI, regardless of your plan. Turning it on sets the scheduler size to Small and turns off high availability (HA). Turn the setting back off before you save to restore your original scheduler size and HA settings.
- The Logs page for a Deployment now includes a Custom Range time filter, so you can search an exact start and end time instead of choosing only from the preset ranges. A custom range can span a maximum of 24 hours, and your selected time range is saved in the URL so you can bookmark or share the view.
The Astro IDE is now generally available and is no longer a Preview feature. The Astro IDE is a browser-based workspace for Apache Airflow where you write Dag code, validate and test changes, and deploy or push your work without setting up a local development environment.
If you route Astro traffic through a forward proxy or secure tunnel, such as Zscaler, you can now turn on Proxy-Aware IP Allowlisting on the IP Access List page to also accept the egress IP address of that proxy or tunnel as a valid match.
Hibernation schedules now display as a visual weekly chart instead of a list of cards or a CRON table. The chart shows every schedule on one week-long timeline, in both UTC and your local time zone, so you can see at a glance when a Deployment will be awake or hibernating.
- Updated Astro infrastructure to improve stability and reliability.
Self-service cross-region disaster recovery (DR) for Azure dedicated clusters is now generally available, which means DR is now available on all three cloud providers. You can configure a primary and a secondary dedicated cluster in different Azure regions, and fail over with minimal downtime and data loss.
Enterprise+ Organizations can now query Astro cost and usage data programmatically through the new List daily usage endpoint on the Astro v1 Labs API , which returns per-Deployment resource cost data with a FOCUS-formatted response option.
Self-service cross-region disaster recovery (DR) for GCP dedicated clusters is now generally available. You can configure a primary and a secondary dedicated cluster in different GCP regions, and fail over with minimal downtime and data loss.
Astro's navigation now gives you a single view across your entire Organization instead of a single Workspace. Deployments, Dags, and Astro IDE projects all appear across Workspaces in one view, with Workspace context on every row. Filter to a specific Workspace when you need to, or work from the full picture across your Organization.
You can now test code in the Astro IDE against an existing Astro Deployment in your Workspace, instead of only an ephemeral test Deployment. Testing against an existing Deployment reuses its configuration, connections, and resources, and skips provisioning a new environment.
Astro now offers a new version of the Deployment analytics experience with expanded Airflow visibility, including API server and webserver metrics, Dag processor coverage, Kubernetes executor and KubernetesPodOperator coverage, parse time, and richer per-status and per-component breakdowns.
- Updated Astro infrastructure to improve reliability and performance.
You can now enable Sub-Second Pipelines on Airflow 3.2+ Deployments that use the Astro executor . Sub-Second Pipelines pair the Astro executor with a dedicated event-driven Event Scheduler that picks up and dispatches API-triggered Dag runs in under a second and sustains approximately 1,000 Dag runs per minute, where the Celery executor queues and falls...
You can now use Otto to review your Airflow code automatically when you open a pull request or merge request. The Otto review action posts a sticky summary comment, adds inline comments where it finds issues, and offers commit suggestions where a concrete fix is available.
- When you add the first IP address range to your organization's IP access list, the Astro API now rejects the request with a 400 Bad Request error if your current IP address falls outside the submitted ranges, which prevents you from accidentally locking yourself out.
Dag-level access control is now generally available. You can assign roles scoped to individual Dags within a Deployment to enforce least-privilege security and enable multiple teams to collaborate in a single Deployment without exposing Dags across team boundaries.
| Release-notes page | Site | Feed |
|---|---|---|
| Astro CLI release notes astronomer.io | astronomer.io | None |
| Astro release notes astronomer.io | astronomer.io | None |
| Astro Runtime release notes astronomer.io | astronomer.io | None |
| Astronomer Software release notes astronomer.io | astronomer.io | None |
| Subscribe to release notes astronomer.io | astronomer.io | None |