-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Active deadline seconds #31146
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
Active deadline seconds #31146
Conversation
…tive_deadline_seconds # Conflicts: # airflow/providers/cncf/kubernetes/operators/pod.py
Can you please update tests for those to include it? |
2 similar comments
Can you please update tests for those to include it? |
Can you please update tests for those to include it? |
@potiuk Sure, I will work on this in a few days |
7e8c59c
to
d4b72de
Compare
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. |
Hi @andyfcx are you still working on this? If not, I would lead it to completion |
I have been too busy to complete my testing on kubernetes, so it would be great if you can complete it, thanks. |
Thank you for the handover, working on it |
This PR exposes
activeDeadlineSeconds
in k8s pod spec as a parameter for user's convenience to set for airflow 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.