The following documents any backwards-incompatible changes in the Airflow Helm chart and assists users migrating to a new version.
Run helm repo update before upgrading the chart to the latest version.
ingress.web.host and ingress.flower.host parameters have been renamed to ingress.web.hosts and ingress.flower.hosts, respectively. Their types have been changed from a string to an array of strings.
The old parameter names will continue to work, however support for them will be removed in a future release so please update your values file.
The default Airflow version that is installed with the Chart is now 2.1.4, previously it was 2.1.2.
ingress.flower.precedingPaths and ingress.flower.succeedingPaths parameters have been removed as they had previously had no effect on rendered YAML output.
With the move to support the stable Kubernetes Ingress API the default path has been changed from being unset to /. For most Ingress controllers this should not change the behavior of the resulting Ingress resource.
Run helm repo update before upgrading the chart to the latest version.
The default Airflow version that is installed with the Chart is now 2.1.2, previously it was 2.0.2.
This chart has dropped support for Helm 2 as it has been deprecated and no longer receiving security updates since November 2020.
webserver.extraNetworkPolicies and flower.extraNetworkPolicies have been renamed to webserver.networkPolicy.ingress.from and flower.networkPolicy.ingress.from, respectively. Their values and behavior are the same.
The old parameter names will continue to work, however support for them will be removed in a future release so please update your values file.
The dags.gitSync.root and dags.gitSync.dest parameters did not provide any useful behaviors to chart users so they have been removed.
If you have them set in your values file you can safely remove them.
The dags.gitSync.excludeWebserver parameter was mistakenly included in the charts values.schema.json. If you have it set in your values file,
you can safely remove it.
The migrateDatabaseJob and createUserJob jobs were incorrectly using the webserver's nodeSelector, affinity
and tolerations (if set). Each job is now configured separately.