Allow automated edge worker maintenance#66310
Merged
jscheffl merged 3 commits intoapache:mainfrom May 4, 2026
Merged
Conversation
Contributor
Author
|
FYI @AutomationDev85 - would be cool having a review from you as well. |
61a7e68 to
c38c484
Compare
eladkal
approved these changes
May 3, 2026
AutomationDev85
approved these changes
May 4, 2026
Contributor
AutomationDev85
left a comment
There was a problem hiding this comment.
I like this Idea!
33e261e to
75b0f80
Compare
79 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sometimes edge workers are known not to be healthy and in #65472 we added an interface that edge workers can report their health state to the reporting.
This PR enables the option that workers - if certain level of health exceeded - turn themself into maintenance. And also optionally can turn operational if the condition resolved.
In such case a system information hook most probably is to be deployed and configured to check for a specific condition (e.g. free disk space). Looks like:

When all is good back again then it looks like:

Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.