-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Fix multiNamespaceMode not working with executor KubernetesExecutor #34505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix multiNamespaceMode not working with executor KubernetesExecutor #34505
Conversation
…utor-KubernetesExecutor
hussein-awala
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a new test which simulates the issue you have with the current implementation? (in this module)
346bd7e to
1819d53
Compare
1819d53 to
6bc7ccf
Compare
Hi @hussein-awala , I have added a test case to test this scenario |
…utor-KubernetesExecutor
hussein-awala
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
…utor-KubernetesExecutor
|
Thank you very much guys for this fix 🙏 |
…utor-KubernetesExecutor
|
helm chart tests are failing |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
Currently, multiNamespaceMode is not working with executor KubernetesExecutor.
Even though we set the pod override in the executor config, the pod is still generated in the airflow namespace.
It is suggested to change the order of this pod list to make it work.
See more details:
#31990
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.