Expose filteredNodes to func PriorityMetadataProducer #84542
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.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Due to some historical reason, some Priorities are not written in the map-reduce style, in particular PodAffinity and EvenPodsSpread. To make sure they can refactored into map-reduce style, their specific internal helper data structure must be calculated in PriorityMetadataProducer, and unfortunately current PriorityMetadataProducer signature doesn't expose the
filteredNoded
, which is needed for those 2 Priorities. This PR adds the additionalfilteredNoded
in PriorityMetadataProducer.Which issue(s) this PR fixes:
The migration of PodAffinity and EvenPodsSpread Priority is dependent on this.
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
/sig scheduling
/assign @ahg-g