I think I see the problem. When you create a standalone pod, it has no OwnerReferences, and the descheduler will not evict any pods without ownerreferences (unless they have the special "evictable" label, see: https://github.com/kubernetes-sigs/descheduler/blob/e2a23f28480b3d439e7049c314a369013699faa1/pkg/descheduler/pod/pods.go#L34)

For that reason, the easiest way to test this would be to create your dedicated-nodes pod with the following annotation:

```
apiVersion: v1
kind: Pod
metadata:
  name: dedicated-nodes
  annotations:
    descheduler.alpha.kubernetes.io/evict: "true"
spec:
  containers:
    - image: "docker.io/ocpqe/hello-pod"
      name: hello-pod
```

This instructs the descheduler that, even though this pod has no ownerreferences, it is evictable. Running this on my own cluster I successfully see the pod evicted

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581