-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Kill kube watcher instance if it doesnt terminate gracefully in 60 seconds #52662
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
Conversation
kosteev
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.
Hi Pavan, did you test this change end to end?
Can you, please, add also unit test for this.
|
Yep. Would be great to get that in - seems that others have similar issue - @pavansharma36 ? |
...cncf/kubernetes/src/airflow/providers/cncf/kubernetes/executors/kubernetes_executor_utils.py
Outdated
Show resolved
Hide resolved
|
Can we submit this change? |
…conds (apache#52662) * Kill kube watcher instance if it doesnt terminate gracefully in 60 seconds * suggested changes --------- Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…conds (apache#52662) * Kill kube watcher instance if it doesnt terminate gracefully in 60 seconds * suggested changes --------- Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…conds (apache#52662) * Kill kube watcher instance if it doesnt terminate gracefully in 60 seconds * suggested changes --------- Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
|
Hi all, was that a bug or was it by design? And if it was a bug, has it been fixed? I am using Airflow version 2.10.4. Please let me know. |
|
Fix was released in kubernetes provider v10.7.0 https://airflow.apache.org/docs/apache-airflow-providers-cncf-kubernetes/stable/changelog.html#id12 Its compaitible with airflow 3.1.0 |
Closes: #52284
^ 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 airflow-core/newsfragments.