Astro Runtime builds on the reliability of Astronomer Certified (AC) with new features that center on usability and performance.
Apache Airflow 2.3 will be the last Airflow version supported by AC. To avoid future disruptions, Astronomer recommends migrating Deployments from AC to Astro Runtime as soon as your organization is ready.
Migrating a Deployment to Astro Runtime is similar to the standard upgrade process. There are no known disruptions when migrating a Deployment from AC to the equivalent version of Astro Runtime.
Differences between Astro Runtime and Astronomer Certified
Functionally, Runtime images are similar to AC images. They both include:
- Timely support for new patch, minor, and major versions of Apache Airflow.
- Support lifecycles that extend beyond those offered by the open source community.
- Regularly backported bug and security fixes.
Astro Runtime includes additional features which are not available in AC images, including:
- Exclusive features for improving task execution, including smart task concurrency defaults and high availability configurations.
astronomer-providerspackage, which is an open source collection of Apache Airflow providers and modules maintained by Astronomer.
- Airflow UI improvements, such as showing the Deployment Docker image tag in the footer of all UI pages.
See Runtime Architecture for more detailed information about Runtime's distribution and features.
All versions of AC have an equivalent version of Astro Runtime. To see the equivalent version of Astro Runtime for a Deployment running AC, open the Deployment in the Software UI and go to Settings. The equivalent version of Astro Runtime is shown in the Migrate to Runtime-[Version number] button.
Step 1: Start the migration process
- In the Software UI, open your Deployment.
- Click the Settings tab and then click Migrate to Runtime-[Version Number].
You can't simultaneously migrate to Astro Runtime and upgrade your Deployment. To upgrade to a later version of Runtime than your equivalent AC version, you must first either upgrade Astronomer Certified or migrate to Astro Runtime before upgrading. For example, the upgrade path from AC 2.2.3 (Airflow 2.2.3) to Runtime 5.0.4 (Airflow 2.3.0) would be:
AC 2.2.3 > AC 2.3.0 > Astro Runtime 5.0.4
If you prefer to use the Astro CLI, you can run
astro deployment runtime migrate --deployment-id=<your-deployment-id> to start the upgrade process.
Step 2: Migrate your Astro project
In your Astro project, open your
FROMline of your project's
Dockerfileto reference a new Astro Runtime image. For example, to migrate to Astro Runtime 5.0.4, you would change the
For a list of currently supported Astronomer images, see:danger
Astronomer does not support Airflow downgrades. After you upgrade your Airflow version, you can't revert to an earlier version.
Optional. Test your migration to Astro Runtime locally by running:
astro dev restart
All 4 running Docker containers for each of the Airflow components restart and begin running your new image.
To confirm that your migration was successful, open the Airflow UI at
localhost:8080and scroll to the bottom of any page. You should see your new Runtime version in the footer.
Step 3: Deploy to Astronomer
To push your migration from Astronomer Certified to Astro Runtime on Astronomer Software, run:
In the Software UI, open your Deployment and click Open Airflow.
Scroll to the bottom of any page. You should see your new Runtime version in the footer.