Bugfix: avoid ext resource less then allocated #892
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?
bugfix
What this PR does / why we need it:
When online pods start using resources, the crane agent will reduce the amount of ext resources. If an online pod uses too many resources, the ext resources may be less than allocated. This can cause pods using ext resources to enter an indeterminate state. At this time, the pods will not be evicted directly, but restarting the kubelet may cause eviction.
This should be a bug. I tried to compare the total amount of allocated ext resources when reporting ext resources. Of course, only running pods are calculated, which is consistent with the logic of the kubelet.
Which issue(s) this PR fixes:
Fixes #890
Special notes for your reviewer: