mirror of
https://github.com/kubernetes-sigs/descheduler.git
synced 2026-01-26 13:29:11 +01:00
75880226c0
Currently, the pod evictor is created during each descheduling cycle to reset the internal counters and the fake client (in case a dry run is configured). Instead, create the pod evictor once and reset only what's needed. So later on the pod evictor can be extended with e.g. a cache keeping the track of eviction requests that are still in progress and required more than a single descheduling cycle to complete.