It was not that soon, but the first PR to move Celery* executors to the celery provider is in https://github.com/apache/airflow/pull/32526. Seems that was rather easy change (as expected)
What will follow once this is merged, is a similar move of kubernetes executor. Why now? We are rather close to 2.7.0 and we do not expect many fixes to be cherry-picked, so this is about the right time to move Kubernetes code (to avoid many conflicts when cherry-picking). I also want to wait with the K8S executor move for https://github.com/apache/airflow/pull/30727 by Nikolas (and being close to 2.7.0 was one of the reasons why we were waiting to merge that one). J. On Sat, Feb 25, 2023 at 2:53 PM Jarek Potiuk <[email protected]> wrote: > The vote has passed. We will be moving the executors soon (about the > same time we complete AIP-51) > > One step closer to making sure Providers are not referred in the Airflow > core. > > Voting summary: > > 8 "+1" binding votes received: > - Jarek Potiuk (binding) > - Ash Berlin-Taylor (binding) > - Josh Fell (binding) > - Elad Kalif (bindig) > - Vikram Koka (binding) > - Ping Zhang (binding) > - Kaxil Naik(binding) > - Pierre Jeambrun(binding) > > 2 "+1+ non-binding votes received: > - Hussein Awala > - Mehta Shubham > > Vote thread: > https://lists.apache.org/thread/7gyw7ty9vm0pokjxq7y3b1zw6mrlxfm8 > > I will open the PRs to move the executors some time soon :) > > J. >
