Closed yuey002 closed 3 months ago
@zryfish two checks are still red, please take a look
@yuey002 Please rebase the code to the main branch, and push again
@NickrenREN All CI checks have passed. Could you help merge this MR when getting a chance? Thank you.
@yuey002 sure, merged, thanks for this fix
For assumed/bound pods, during add, update, and delete events, they do not enter the scheduler queue but instead trigger the AssignedPodAdded function. If, due to pod affinity-related reasons, a pod in the unschedulable queue becomes schedulable, then this unschedulable pod can be moved from the unschedulable queue to the ready or backoff queue for scheduling retries.
Therefore, the current naming of addAssumedOrBoundPodToQueue/updateAssumedOrBoundPodInQueue/deleteAssumedOrBoundPodInQueue is ambiguous, because the pod is not actually added to the scheduler queue, but triggers an update from the unschedulable queue to the ready/backoff queue. Hence, the functions are renamed to triggerQueueOnAssumedOrBoundPodAdd/triggerQueueOnAssumedOrBoundPodUpdate/triggerQueueOnAssumedOrBoundPodDelete.