Bug 1798500

Summary:	Descheduler operator does not support RemovePodsViolatingNodeTaints strategy
Product:	OpenShift Container Platform	Reporter:	Mike Dame <mdame>
Component:	kube-scheduler	Assignee:	Mike Dame <mdame>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, mfojtik, yinzhou
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:33:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Dame 2020-02-05 14:02:51 UTC

Currently in the descheduler operator readme (and code) there is no way to enable the RemovePodsViolatingNodeTaints strategy. This should be added to bring feature parity up-to-date with the descheduler

Comment 4 Mike Dame 2020-02-06 21:21:41 UTC

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

Comment 7 errata-xmlrpc 2020-05-04 11:33:47 UTC

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