Skip to main content
Version: 0.16

Astronomer v0.16 Release Notes

Notice on Astronomer Software Releases

This document includes all release notes for Astronomer Software v0.16.

For instructions on how to upgrade to the latest v0.16 patch version of Astronomer, read Upgrade to a Stable Version of Astronomer. If you're interested in upgrading from Astronomer v0.16.x to the latest LTS version of the platform, read Upgrade to Astronomer Software v0.23.

We're committed to testing all quarterly Astronomer Software versions for scale, reliability and security on EKS, GKE and AKS. If you have any questions or an issue to report, don't hesitate to [reach out to us]((

Astronomer v0.16

Latest Patch Release: v0.16.15


Release date: December 11, 2021

Bug Fixes

  • Remediated CVE-2021-44228 related to Log4J by setting ES_JAVA_OPTS=-Dlog4j2.formatMsgNoLookups=true at runtime for all ElasticSearch containers


Release Date: November 3, 2021

Bug Fixes

  • Fixed a security issue where an internal API endpoint could be accessed by an unauthorized user with a specific event input


Release Date: January 5, 2021

Support for Airflow 1.10.14

Airflow 1.10.14 was built to make testing and migration to Airflow 2.0 as easy as possible. Highlights include:

  • "Warning" to users with duplicate Airflow Connections (commit)
  • Enable DAG Serialization by default (commit)
  • Support for Airflow 2.0 CLI commands (commit)
  • Bugfix: Unable to import Airflow plugins on Python 3.8 (commit)
  • BugFix: Tasks with depends_on_past or task_concurrency are stuck (commit)
  • Security Fix: Incorrect Session Validation in Airflow Webserver with default config allows a an authorized Airflow user on site A access an unauthorized Airflow Webserver on Site B through the session from Site A. (Details)

To upgrade to AC 1.10.14, add our new Debian image to your Dockerfile:


For detailed guidelines on how to upgrade Airflow on Astronomer, read Upgrade Airflow. For more information on 1.10.14, check out the Airflow Release or the corresponding AC 1.10.14 changelog.

Note: In an effort to standardize our offering and optimize for reliability, we will only support a Debian-based image for AC 1.10.14. Alpine-based images for AC 1.10.5 - 1.10.12 will continue to be supported. For guidelines on how to migrate from Alpine, go to Upgrade Airflow.

Support for latest Astronomer Certified Patch Releases

In addition to support for Airflow 1.10.14, Astronomer v0.16.15 also includes support for the latest patch versions of existing Astronomer Certified images:

For instructions on how to upgrade to the latest patch version of a release, refer to Upgrade Airflow.

Support for Docker Images on + DockerHub

Astronomer recently migrated from Docker Hub to as our platform’s primary Docker Registry in light of Docker Hub’s new rate-limit policy, effective Nov 2nd, 2020.

Astronomer v0.16.15 supports Docker images that are pulled from either Docker registry, though we strongly encourage users to switch to images to avoid rate limiting errors from Docker Hub. This change affects both Airflow images (ap-airflow) as well as all Docker images required to run the Astronomer platform, including ap-grafana, ap-registry, ap-pgbouncer, etc. If you're running a legacy Airflow image that pulls from astronomerinc/ap-airflow, for example, all it takes is modifying that image in your Dockerfile to read Both have the exact same functionality.

For more information, refer to Upgrade Apache Airflow on Astronomer or this forum post.

Bug Fixes & Improvements


Release Date: November 16, 2020

Bug Fixes & Improvements

  • BugFix: Typo in Pod Security Policy (PSP) for Private CA


Release Date: November 2, 2020

Bug Fixes & Improvements
  • BugFix: Fix conditionally disabling subcharts


Release Date: October 30, 2020

Support for Custom CA Certificates

For users who rely on an internal Certificate Authority (CA), Astronomer now supports mounting custom CA certificates.

For guidelines, refer to our forum post on "Using Private CAs on Astronomer".

Bug Fixes & Improvements

  • Improvement: New Houston API mutation that allows users to enable or disable KEDA (updateDeploymentKedaConfig)
  • BugFix: Alerts from Astronomer not sent when an Airflow component breaches the resource threshold level defined in Prometheus


Release Date: October 8, 2020

Support for Airflow 1.10.12

Astronomer v0.16.9 comes with support for Airflow 1.10.12 in addition to 3 patch versions of previously released images.

Airflow 1.10.12 notably includes:

  • The ability to configure and launch pods via YAML files with the Kubernetes Executor and KubernetesPodOperator (commit)
  • A new on_kill method that ensures a KubernetesPodOperator task is killed when it's cleared in the Airflow UI (commit)
  • Ability to define a custom XCom class (commit)
  • Support for grabbing Airflow configs with sensitive data from Secret Backends (commit)
  • Support for AirfowClusterPolicyViolation support in Airflow local settings (commit).

For a detailed breakdown of all changes, refer to the AC 1.10.12 Changelog. For instructions on how to upgrade to 1.10.12 on Astronomer, refer to "Airflow Versioning".

Note: AC 1.10.12 will be the last version to support an Alpine-based image. In an effort to standardize our offering and optimize for reliability, we'll exclusively build, test and support Debian-based images starting with AC 1.10.13. A guide for how to migrate from Alpine to Debian coming soon.

Support for Latest Builds of Astronomer Certified

Astronomer v0.16.9 also includes support for:

These patch releases include a fix to an identified security issue listed here.

Bug Fixes and Improvements

Two additional bugs were addressed in Astronomer v0.16.9:

  • BugFix: IAM role integration fails with Debian Airflow Image on DAG run ([Errno 13] Permission denied)
  • BugFix: Calling the createWorkspace Houston API mutation with a system Service Account returns an error (No Node for the model User)


Release Date: September 25, 2020

Export Logs from Fluentd to Amazon S3

Astronomer leverages Fluentd as a data collector that is responsible for scraping and cleaning Airflow task logs to then send to Elasticsearch, a search engine used to centralize and index logs from Airflow. As of v0.16, Astronomer now supports a Fluentd to S3 plugin that allows users to forward Airflow logs to Amazon S3 while ensuring they're also sent to Elasticsearch and otherwise supported by the platform.

For step-by-step guidelines, refer to "Forward Logs to S3".


Release Date: September 9, 2020

Bug Fixes and Improvements

  • BugFix: Adding a non-Airflow config Environment Variable on Software UI with KubernetesExecutor does not get passed successfully


Release Date: September 4, 2020

Allow Users to Define Custom Platform and Airflow Deployment-level Alerts in config.yaml

Astronomer v0.16.6 allows users to define custom alerts via the config.yaml file and successfully pass those to Prometheus, a monitoring tool that Astronomer uses to collect metrics from a variety of endpoints and push them to Grafana for visualization.

For example, you might want to add an Airflow alert to fire if a Deployment has been using over 50% of its pod quota for over 10 minutes or a Platform alert if more than 2 Airflow Schedulers don't heartbeat for more than 5 minutes. Here's what your config.yaml might look like:

airflow: |
- alert: ExampleAirflowAlert
expr: (sum by (release) (kube_resourcequota{resource="pods", type="used"}) / sum by (release) (kube_resourcequota{resource="pods", type="hard"})*100) > 50
for: 10m
tier: airflow
component: deployment
workspace: {{ printf "%q" "{{ $labels.workspace }}" }}
deployment: {{ printf "%q" "{{ $labels.deployment }}" }}
summary: {{ printf "%q" "{{ $labels.deployment }} is near its pod quota" }}
description: {{ printf "%q" "{{ $labels.deployment }} has been using over 50% of its pod quota for over 10 minutes." }}
platform: |
- alert: ExamplePlatformAlert
expr: count(rate(airflow_scheduler_heartbeat{}[1m]) <= 0) > 2
for: 5m
tier: platform
severity: critical
summary: {{ printf "%q" "{{ $value }} airflow schedulers are not heartbeating" }}
description: "If more than 2 Airflow Schedulers are not heartbeating for more than 5 minutes, this alarm fires."

For more information on alerts that are generated by default, refer to our "Alerts" doc.

Note: These alerts are NOT Airflow task-level alerts that require definition at the Airflow code level. For more information on how to set up email_on_failure within Airflow, for example, refer to our "Airflow Alerts" doc.

Bug Fixes and Improvements

  • Improvement: Collect kube-dns metrics and add corresponding dashboard in Grafana
  • Improvement: Optimize DNS queries to reduce traffic by providing a pgbouncer FQDN suffixed by a period
  • BugFix: Error on $ astro dev init if not authenticated to Astronomer: "Failed to get list of supported tags from Astronomer" (CLI v0.16.4)
  • BugFix: $ astro upgrade incorrectly indicates that the user is running the latest version of the CLI if running < v0.10.0 of the CLI (CLI v0.16.4)
  • BugFix: Environment Variable changes via the Software UI not consistently reflected in Workers and in underlying Kubernetes secrets
  • BugFix: Incorrect Extra Capacity AU detected from Houston API
  • BugFix: Port prometheus-postgres-exporter and prometheus-node-exporter pod security policy (PSP) logic under global pspEnabled: flag


Release Date: August 19, 2020

Support for Latest Builds of Astronomer Certified

Astronomer Software v0.16.5 includes support for the following patch releases of Astronomer Certified (AC), our distribution of Apache Airflow:

These patch releases most notably include:

  • BugFix: Broken /landing_times view in the Airflow UI rendering with plain HTML (commit)
  • BugFix: Tighten restriction for apache-airflow in requirements.txt to allow users to install other packages with that prefix (commit)
  • BugFix: Broken PapermillOperator (1.10.10 only).

For information on how to upgrade Astronomer Certified versions, refer to our "Manage Airflow Versions" doc.

Airflow Chart: Improved Upgrade Process

Historically, upgrades to Astronomer (major, minor or patch) that have included a change to the Airflow Chart forcibly restart all Airflow Deployments running on the platform at the time of the upgrade, often causing task interruption.

This change allows for Airflow Deployments to remain unaffected through the upgrade and for Airflow Chart changes to take effect only when another restart event is triggered by a user (e.g. a code push, Environment Variable change, resource or executor adjustment, etc).

More specifically, this changes the behavior of our API's updateDeployment mutation to perform the Airflow Helm Chart version upgrade only if/when a Houston config is updated.

Bug Fixes and Improvements

  • BugFix: 400 Error on $ astro workspace user add in Astronomer CLI (CLI v0.16.3)
  • BugFix: 400 Error on $ astro workspace user remove in Astronomer CLI (CLI v0.16.3)
  • BugFix: Users able to create 2+ Service Accounts with the same label
  • BugFix: Link to Workspace broken in 'SysAdmin' > 'Users' View
  • BugFix: Navigating directly to the 'Metrics' Tab of the Software UI renders error
  • BugFix: Adjust commander role to include KEDA CRD (fixes could not get information about the resource: on Airflow Deployment creation)


Release Date: July 22, 2020

  • BugFix: Restore ability to dynamically pull namespace with namespace=default in [KubernetesPodOperator] and KubernetesExecutor Config
  • BugFix: Error on $ astro dev init and $ astro version if not authenticated to Astronomer (CLI v0.16.2)


Release Date: July 22, 2020

  • Improvement: Allow SysAdmins to Access Workspaces in the Astro UI
  • Improvement: Create new critical severity alerts for platform system components
  • BugFix: Emails caps-sensitive in error for ADFS
  • BugFix: Mismatched rendering when switching between Deployments in the Astro UI


Release Date: July 9, 2020

  • BugFix: 'Metrics' Tab in the Astro UI unresponsive with large task payload
  • BugFix: Error when deleting a 'Pending' Workspace invite in Astro UI
  • BugFix: "Deployment Status" bubble in the Astro UI persistently blue/pulsating
  • BugFix: Issue with Extra Capacity resetting every time you change an Env Var


Release Date: June 29, 2020

New "Environment Variables" Tab in the Software UI

Astronomer v0.16 comes with significant improvements to the experience of setting Environment Variables on Astronomer. Namely, we've introduced a dedicated 'Variables' tab, lessening the density of the "Settings" page and making these configurations accessible to "Trial" users on Astro.

With the new tab comes the ability for Workspace Admins and Editors to create and mark a value as 'secret', permanently hiding the value from the Software UI (and from the client). From the same tab, users can now export Environment Variables as 'JSON' as well.

For more details on this new feature, reference our "Environment Variables" doc.

Support for AD FS

Astronomer v0.16 for Astronomer Software users comes with support for Microsoft's Active Directory Federation services (AD FS), as an alternative authentication system.

To learn more, reference "Auth Systems on Astronomer".

Bug Fixes and Improvements

  • BugFix: Add Alphanumeric characters (e.g. S3)to Environment Variable validation in the Astro UI
  • BugFix: ExtraCapacity values (over minimum) are overridden in Deployment Update
  • Improvement: Simplify updateUser Mutation in Houston API (remove uuid)
  • Security: Implement platform-wide Pod Security Policies
  • Security: Clear Javascript CVEs
  • BugFix: "Airflow State" dashboard in Grafana broken
  • BugFix: CLI Install command should point to BASEDOMAIN (not for Software users
  • BugFix: SysAdmin can't revoke SysAdmin permissions from another user

Astronomer v0.15

Release Date: June 8, 2020


Support for Airflow 1.10.10

As of v0.15, Astronomer users are free to run our Astronomer Certified (AC) 1.10.10 image, which is based on the Airflow 1.10.10 open source version released in early April.

Airflow 1.10.10 notably includes the ability to choose a timezone in the Airflow UI, DAG Serialization functionality for improved Webserver performance, and the ability to sync Airflow Connections and Variables with a Secret Backend tool (e.g. AWS Secret Manager, Hashicorp Vault, etc.)

For more detail on what's included in AC 1.10.10, reference the changelog.

Ability to Set Custom Release Names

As of Astronomer v0.15, Software customers can now customize the release name of any Airflow Deployment instead of relying on the default naming scheme (e.g. solar-galaxy-1234). Release names within a single cluster must be unique and will continue to be immutable following creation.

To activate this feature on the platform, refer to the manualReleaseNames value in your config.yaml.

Ability to Annotate Pods to integrate with IAM Roles

As of Astronomer v0.15, IAM roles can now be appended to all pods within any individual Airflow Deployment on the platform. Users who integrate Airflow with some resource or set of resources (e.g. an AWS S3 bucket or Secret Backend) can now configure them to be accessible only to a subset of Kubernetes pods within your wider Astronomer cluster.

Leverage this feature by specifying an existing IAM role arn when you create or update an Airflow Deployment via the Astronomer CLI. For guidelines, go here.

Bug Fixes & Improvements

A few notable bug fixes and improvements:

  • Ability to add multiple email addresses to receive deployment-level alerts
  • Security improvements to the Software UI
  • Reframe "Extra Capacity" in the 'Deployment Configuration' tab of the Software UI
  • Improved error handling for users who sign up with an email different than their input in our trial form
  • Bug Fix: Warning via the CLI on Debian images
  • Bug Fix: "Failed to authenticate to the registry..." error on v0.13 of the CLI
  • Added support for AWS S3 Registry Backend
  • New UI warning when SMTP credentials are not configured and email invites cannot be sent
  • Improved UX of Failed Network Connections
  • Bug Fix: Missing "Deployment" label in Airflow Alerts