Coming from KubeVirt: https://github.com/kubevirt/community/pull/258

The descheduler eviction policy is built on top of the eviction API. The API currently does not support eviction requests that are not completed right away. Instead, any eviction needs to either succeed or be rejected in response. Nevertheless, there are cases where an eviction request is expected to only initiate eviction. While getting confirmation or rejection of the eviction initiation.

The current PoC implementation is located under https://github.com/ingvagabund/descheduler/tree/eviction-in-background-code.

*PoC DoD*:

• eviction in background based on annotation
• eviction in background cancellation and resuming
• internal cache of evictions in background in progress implemented
• limits per node and namespaces respected
• removal of pending assumed evictions in progress
• enable the feature through a new feature gate
• e2e for the eviction in background (with kubevirt deployed to simulate various cases)
• integration with KubeVirt