You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 10, 2022. It is now read-only.
Features like OAuth/LDAP Group Sync likely won't get back-ported to Airflow 1.10.X [1], so if we care about providing the ability for customers to deploy Airflow properly in a multi-tenant environment we should probably take a look at upgrading (or at least providing a compatible branch) for the 2.0 Airflow community image.
I've done some testing and besides changing the build process, the only glaring incompatibilities between the Puckel image (ours) and the new community image is how some of the service environment variables are injected into the container at runtime. We should be able to easily shim around this using environment variable templating.
Another thing I've noticed in testing 2.0 is that
airflow worker
Has changed to the more specific:
airflow celery worker
So we'll need to address that in the worker code as well.
Features like OAuth/LDAP Group Sync likely won't get back-ported to Airflow 1.10.X [1], so if we care about providing the ability for customers to deploy Airflow properly in a multi-tenant environment we should probably take a look at upgrading (or at least providing a compatible branch) for the 2.0 Airflow community image.
I've done some testing and besides changing the build process, the only glaring incompatibilities between the Puckel image (ours) and the new community image is how some of the service environment variables are injected into the container at runtime. We should be able to easily shim around this using environment variable templating.
Another thing I've noticed in testing 2.0 is that
Has changed to the more specific:
So we'll need to address that in the worker code as well.