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(helm): set worker safeToEvict properly #35130
Conversation
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
|
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.
Yeah, it's better than the current implementation, could you add a test for it with the different values?
Thank you so, @hussein-awala I tested the Helm Chart itself with
We got
And
We got
And default values are same than Please, tell me if you know more ways to check it out. |
@hakuno, Hussein meant a test in our test suit to make sure this doesn't regress. Here is an example, and some details on our helm chart tests. |
@jedcunningham Thanks for that. Unfortunately, I've had some difficult to setup this test environment. Thoughts? |
If you do not write what kind of difficulties you had, It's hard to have more thoughts. But I recommend to follow the steps in https://github.com/apache/airflow/blob/main/CONTRIBUTORS_QUICK_START.rst to setup breeze and then the docs pointed at by @jedcunningham provide a step-by-step (almost wizard-like) approach to make it works. |
Thanks, @potiuk - I meant the environment setup itself. My Pytest couldn't discovery tests etc. I'll read that docs as soon as possible... thanks again :) |
@jedcunningham @hussein-awala @potiuk I got it.
Ps. I ran |
Ps.¹ Other Airflow components also has Ps.² At another moment, I see I can contribute with other PRs. Because |
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
It improves (or fixes) the
workers.safeToEvict
usage.Kubernetes administrators/users agree that
cluster-autoscaler.kubernetes.io/safe-to-evict
can be managed to avoid the Autoscaler to kill the worker pod when scaling nodes down.So, if I set
workers.safeToEvict
tofalse
, it gets nothing. The Autoscaler will kill that still. Because the Helm chart has no effect on handling that. See:What about if I need to set that to false? I couldn't. Anybody is unable to.
A probaly workaround would set up
workers.podAnnotations
with map of annotations andworkers.safeToEvict
falsely together.Please, check it out carefully. Thanks in advance!