Remove calls to GetRequirements
where possible
#2608
Merged
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 implementation of
GetRequirements
forapi.Job
allocates new structs, which we'd like to avoid:armada/pkg/api/util.go
Lines 109 to 145 in fac9411
Many of the calls to
GetRequirements
(orPodRequirementFromLegacySchedulerJob
) don't actually need the entireJobSchedulingInfo
; I've replaced them by more granular access. There are still a couple of calls toPodRequirementFromLegacySchedulerJob
in parts of the code that deal with the node database; I'd like to get rid of those separately.I've also renamed
GetRequirements
toGetJobSchedulingInfo
.