-
Notifications
You must be signed in to change notification settings - Fork 674
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
Feature/add pod pending timeout config #4590
Conversation
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
Signed-off-by: Paul Dittamo <[email protected]>
I accidentally ruined https://github.com/flyteorg/flyte/pulls?q=is%3Apr+is%3Aclosed with a rebase and figured it'd be easier to just checkout a new branch
The function only ever returns nil for the error as did the DemystifyPending previously. The linter for some reason flags when the function is not getting exported, so I removed the error return param from the helper. I can also do that for the DemystifyPending function as that only ever returns nil errors as well. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4590 +/- ##
=======================================
Coverage 58.98% 58.99%
=======================================
Files 621 621
Lines 52483 52498 +15
=======================================
+ Hits 30959 30969 +10
- Misses 19057 19062 +5
Partials 2467 2467
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Paul Dittamo <[email protected]>
Tracking issue
#1149
Why are the changes needed?
Users aren't able to configure timeout for pending pods. This leads for pods/tasks stuck in pending to rely upon execution timeout to fail.
PodPendingTimeout can help in situations when pods aren't getting executed due to resources not being available or when downstream execution engines are not able to schedule work.
What changes were proposed in this pull request?
Introduce a "pod-pending-timeout" plugin config to enable users to set pending/queued timeouts for tasks. This value defaults to 0 such that the current pending behavior does not change unless the config is set.
How was this patch tested?
Added unit test here
Setup process
Configure plugins -> k8s -> pod-pending-timeout in flyte_single_binary.yaml
Screenshots
Check all the applicable boxes
(should be auto updated running script/generate_config_docs.sh)
Related PRs
Docs link