This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
Improve the Kubernetes Resource handling #3664
Merged
Conversation
This file contains 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
nwangtw
approved these changes
Jan 13, 2021
`requiredResource` and `scheduledResource` were always the same value
|
lgtm. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The previous Heron Kubernetes Scheduler calculated a homogenous PackingPlan and used the resulting
ScheduledResourcewhich had the "max" cpu and memory. TheRequiredResourcewas never used. This Pull Request updates the logic in the Heron Kubernetes Scheduler to use both sets ofResourceobjects. TheRequiredResourcewill be used as theV1ResourceRequirementsRequestand theScheduledResourcewill continue to be set as theV1ResourceRequirementsLimit.