-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Add active_deadline_seconds
parameter to KubernetesPodOperator
#33379
Conversation
Needs conflict resolution and fixes in tests ... |
@potiuk I fixed the tests as well as rebased it. Can you take a look when free? |
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.
I pushed a commit hoping it might fix the failed test. LGTM
active_deadline_seconds
parameter to KubernetesPodOperator
@hussein-awala seems like the commit didn't do the trick here. I pushed a new fix now, might just do the trick now |
Nope. Seems like it break our K8S tests. FYI. There is a recipe how to setup the environment for K8S tests locally with breeze including step-by-step explanation and example (and Breeze's k8s is really a wizard-like setup that hand-holds you while setting the environment up). https://github.com/apache/airflow/blob/main/TESTING.rst#kubernetes-tests |
🎉 |
Silly mistake by me. Thanks Hussein! |
Thanks @amoghrajesh |
Building on top of #31146 to introduce the
active_deadline_seconds
for airflow KPO launched job pods.^ 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.rst
or{issue_number}.significant.rst
, in newsfragments.