Prevent legacy hybrid executors to be running in Airflow 3 #51733
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:providers
provider:celery
provider:cncf-kubernetes
potiuk
reviewed
Jun 14, 2025
...cncf/kubernetes/src/airflow/providers/cncf/kubernetes/executors/local_kubernetes_executor.py
Outdated
Show resolved
Hide resolved
jscheffl
force-pushed
the
bugfix/prevent-old-hybrid-executors-to-run-in-airflow-3
branch
from
4345b6e to
e7c8af5
Compare
potiuk
approved these changes
Jun 14, 2025
amoghrajesh
approved these changes
Jun 14, 2025
eladkal
approved these changes
Jun 14, 2025
XD-DENG
approved these changes
Jun 14, 2025
jscheffl
deleted the
bugfix/prevent-old-hybrid-executors-to-run-in-airflow-3
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Slack we had multiple chats/threads/discussions about broken executors in Airflow 3 (e.g. https://apache-airflow.slack.com/archives/C07813CNKA8/p1749747275499659) and as in #51715 docs were updated this PR also prevents running them in Airflow 3++. See also #47322
This PR also adds a safeguard into the executor code to block execution if somebody still does not read docs.
@eladkal do you think this would be able to slip into preparation of provider cuts?