descheduler: check nodemetrics cr is expired or not when descheduling #1721
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.
Ⅰ. Describe what this PR does
case:
The nodemetric cr has not been updated for a long time, e.g. the koordlet was deleted, but the load information written last time is particularly high, causing pods on this node being evicted all the time, even though the actual load was low.
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
check nodemetrics cr is expired or not when descheduling
Ⅳ. Special notes for reviews
V. Checklist
make test