Astronomer Software ships with and requires a number of adjacent technologies that support it, including Kubernetes, Helm, and Apache Airflow itself. This guide provides a reference of all required tools and versions for running Astronomer Software.
While the tables below reference the minimum compatible versions, we typically recommend running the latest versions of all tooling if and when possible.
The following table shows version compatibility information for all currently supported versions of Astronomer Software and some legacy versions. Check Astronomer Software lifecycle schedule for more information about supported versions of Astronomer Software.
See Kubernetes version support table and policy for Astronomer platform compatibility with Kubernetes.
Astronomer does not support Postgres versions that are beyond their end-of-life date. You can check to see the currently supported versions of Postgres.
Astronomer recommends using the latest available version of the Astro CLI for all Software versions, in most cases. To upgrade from an earlier version of the CLI to the latest, see Upgrade to Astro CLI version 1.0+.
For more detail about the changes in each Astronomer Software release, see the Astronomer Software Release Notes.
Only Astronomer-distributed images supporting Airflow 2.x are compatible with all versions of Astronomer Software. Astro Runtime maintenance is independent of Software maintenance. For more information, see Astro Runtime maintenance and lifecycle policy.
In general, Astronomer Software will support a given version of Kubernetes through its End of Life. This includes Kubernetes upstream and cloud-managed variants like GKE, AKS, and EKS. When a version of Kubernetes reaches End of Life, support will be removed in the next major or minor release of Astronomer Software. For more information on Kubernetes versioning and release policies, refer to Kubernetes Release History or your cloud provider.
See the following table for all supported Kubernetes versions in each maintained version of Astronomer Software.
If there are no workloads running on the nodes you want to upgrade, there won’t be an immediate impact on the Astronomer or Airflow components during the initial phase of upgrading your managed node groups. To minimize disruptions, however, perform a controlled rollout restart of the worker nodes. During your controlled rollout, monitor the health of the new nodes and workloads before decommissioning the old nodes.
Before beginning the upgrade process, ensure you have all necessary backups ready. After upgrading, verify that all Astronomer and Airflow components are running as expected on the new nodes. After the Astronomer version is compatible with the EKS/AKS Cluster, you don’t need to change you Astronomer configurations or settings. However, the upgrade requires restarting the Kubelet on each node, which causes the Astro and Airflow components to also restart.
For more information on upgrading Kubernetes versions, follow the guidelines offered by your cloud provider.
Astronomer Software Deployments utilize the Astronomer-distributed Helm chart for Apache Airflow. A Deployment’s Airflow chart defines how a Deployment autoscales Pods and interacts with other components in your cluster.
Use the following table to see the Airflow Helm chart version for each supported version of Astronomer Software. To view the Airflow Helm chart for an unsupported version of Astronomer Software, open the default Astronomer Helm chart in the astronomer/astronomer repository and select the Tag that corresponds to the unsupported version. The value of airflowChartVersion is the Airflow Helm chart version.
The following table shows version compatibility information for all versions of Astronomer Software which are no longer supported:
¹ Support for some Kubernetes versions is limited to specific Astronomer Software patch versions. You can find the specific versions supported by a particular Software patch starting with version 0.32.4 in the Release index.