-
Notifications
You must be signed in to change notification settings - Fork 696
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
Upstream: Ensure that k8s plugins (dask, kfoperator) have resource requests and limits set #6264
Upstream: Ensure that k8s plugins (dask, kfoperator) have resource requests and limits set #6264
Conversation
Signed-off-by: Katrina Rogan <[email protected]>
Code Review Agent Run #3b164dActionable Suggestions - 5
Review Details
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6264 +/- ##
==========================================
- Coverage 36.86% 36.85% -0.01%
==========================================
Files 1318 1318
Lines 134773 134782 +9
==========================================
- Hits 49683 49679 -4
- Misses 80758 80771 +13
Partials 4332 4332
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Changelist by BitoThis pull request implements the following key changes.
|
Why are the changes needed?
When a user specifies dask scheduler or worker requests, but not limits, k8s pod scheduling fails with
What changes were proposed in this pull request?
This change follows existing container and k8s pod task logic to ensure that when one of requests or limits are not set, the unspecified value comes from the specified one, or otherwise both values come from the platform defaults.
How was this patch tested?
Ran locally on a flyte deployment, verified after changes that worker pods god scheduled
Labels
Please add one or more of the following labels to categorize your PR:
This is important to improve the readability of release notes.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
This PR enhances Kubernetes resource management by implementing proper resource requests and limits handling through a new ApplyK8sResourceOverrides utility. The changes focus on preventing pod scheduling failures in quota-restricted environments by ensuring both CPU and memory limits are properly specified. The implementation includes safeguards for platform-defined defaults when values are unspecified.Unit tests added: True
Estimated effort to review (1-5, lower is better): 2