This story serves as a placeholder for providing instructions on how to deploy the descheduler (and its operator) with the new EvictionsInBackground alpha feature enabled.

Minimal testing use cases:

• the descheduler respects the eviction API error produced by kubevirt vm live migration
• the descheduler does not evict all vm pods when exercising the LowNodeUtilization strategy
• etc.

Images available for testing:

• descheduler with EvictionsInBackground feature implemented: quay.io/jchaloup/descheduler:4.17.0-evictions-in-background
• descheduler operator allowing to enable EvictionsInBackground feature: quay.io/jchaloup/cluster-kube-descheduler-operator:4.17.0-evictions-in-background

How to test it:

1. kubevirt is installed and ready
2. update https://github.com/openshift/cluster-kube-descheduler-operator/blob/master/deploy/05_deployment.yaml to point to both new images
   • .spec.template.spec.containers[0].image to point to quay.io/jchaloup/cluster-kube-descheduler-operator:4.17.0-evictions-in-background
   • .spec.template.spec.containers[0].env["RELATED_IMAGE_OPERAND_IMAGE"] to point to quay.io/jchaloup/descheduler:4.17.0-evictions-in-background
3. update https://github.com/openshift/cluster-kube-descheduler-operator/blob/master/deploy/02_kube-descheduler-operator.cr.yaml
   • enable the right profiles + customization if needed
   • set .spec.profileCustomizations.featureGates to ["EvictionsInBackground"]
4. deploy manifests under https://github.com/openshift/cluster-kube-descheduler-operator/blob/master/deploy
5. run any test you need to run