Bug 1989722 - Descheduler operator should allow eviction based on soft topology constraints
Summary: Descheduler operator should allow eviction based on soft topology constraints
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.0
Assignee: Mike Dame
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-03 19:38 UTC by Mike Dame
Modified: 2021-10-18 17:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Descheduler now allows pods with soft topology constraints to be evicted by the SoftTopologyAndDuplicates profile
Clone Of: 1989720
Environment:
Last Closed: 2021-10-18 17:44:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-descheduler-operator pull 197 0 None None None 2021-08-03 19:39:16 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:44:37 UTC

Description Mike Dame 2021-08-03 19:38:20 UTC 
The Descheduler operator should provide users with the ability to evict pods using soft (`ScheduleAnyway`) topology spread constraints. This is possible upstream, but needs to be exposed as an option (or additional profile) in the operator
Comment 2 RamaKasturi 2021-08-09 16:06:24 UTC 
currently blocked on this due to bug https://bugzilla.redhat.com/show_bug.cgi?id=1990603
Comment 3 RamaKasturi 2021-08-14 16:39:23 UTC 
Hello Mike,

   I have a question related to SoftTopologyAndDuplicates / TopologyAndDuplicates. I have performed below tests.

First Test:
=========================
1) Enabled SoftTopologyAndDuplicates
2) created  pods according to test [1], WhenUnsatisfiable set to "ScheduleAnyway"
3) I see that pods got evicted due to PodTopologySpread

Second Test:
======================
1) Enabled SoftTopologyAndDuplicates
2) created pods according to test [2] , WhenUnsatisfiable set to "DoNotSchedule"
3) I see that pods got evicted in a similar fashion.

I expected SecondTest not to evict any pods as the profile set here is "SoftTopologyAndDuplicates", could you please help confirm why the pods got evicted even though the profile set was "SoftTopologyAndDuplicates" ? 

[1] https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-43283
[2] https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-40055

Thanks
kasturi
Comment 4 Mike Dame 2021-08-16 14:28:43 UTC 
@Rama The SoftTopologyAndDuplicates profile will evict both ScheduleAnyway AND DoNotSchedule pods, so this is working as expected.
Comment 5 RamaKasturi 2021-08-23 09:26:56 UTC 
Thanks Mike, Moving the bug to verified state based on comment 3 & comment 4.
Comment 8 errata-xmlrpc 2021-10-18 17:44:27 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759
Note You need to log in before you can comment on or make changes to this bug.