Kubernetes: allow opt-out of rescheduling on SIGTERM by setting PREFECT_FLOW_RUN_EXECUTE_SIGTERM_BEHAVIOR#19223
Merged
desertaxle merged 1 commit intoOct 20, 2025
Conversation
…EXECUTE_SIGTERM_BEHAVIOR
354232d to
404e097
Compare
desertaxle
approved these changes
Oct 20, 2025
Member
desertaxle
left a comment
There was a problem hiding this comment.
Hey @svatopluk-sperka! This looks great! Thanks for taking the time to submit a fix!
Contributor
Author
|
That was smooth. Thanks @desertaxle! |
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.
closes #18867.
Gist of the problem is that currently there is no way to opt-out of rescheduling a flow run on SIGTERM. Either:
backoffLimit > 0in which case the K8s retries the jobbackoffLimit = 0in which case Prefect forces reschedule behaviour on SIGTERM via settingPREFECT_FLOW_RUN_EXECUTE_SIGTERM_BEHAVIOR=rescheduleIn our case, we have workflows that we want to reschedule with human in the loop when killed due to eviction. That is because processes triggered downstream currently cannot be cancelled and multiple runs of those processes cause all sorts of problems.
The way I've tried to address the problem is by not forcing
PREFECT_FLOW_RUN_EXECUTE_SIGTERM_BEHAVIOR=reschedulewhen that var is already set in env.My perspective of Prefect codebase is very limited at this point so I'd appreciate any guidance on this one.
Checklist
<link to issue>"mint.json.