-
Bug
-
Resolution: Done
-
Major
-
None
-
4.12.0
-
None
-
Important
-
None
-
Proposed
-
False
-
-
NA
Description of problem:
Descheduler SoftTopologyAndDuplicates uses Stategy RemovePodsViolatingTopologySpreadConstraint which has invalid mapping
Version-Release number of selected component (if applicable):
4.12
How reproducible:
Always
Steps to Reproduce:
1. Create a three node cluster 2. Create a SoftTopologyAndDuplicates Descheduler Operator Policy (KubeDescheduler) 3. Assign three labels to the nodes (w0: zone=a, w1: zone=b, w3: zone=b) 4. create 4 replica sets (you may need to cordon w3 5. Reassign the label for w1 to zone=a 6. Uncordon w3 7. You see no log data on the descheduler showing the pod was evicted.
Actual results:
No rebalancing occurs
Expected results:
The zones should rebalance within the maxskew
Additional info:
This worked in 4.11 and not 4.12 as of: https://github.com/openshift/descheduler/commit/674bf4655d71f4674ee5c111f29903905f985e1e#diff-548663336f315a426f99e4cee346e72f48e31820fd5dba6fac5e4acd289a0506R194 https://github.com/openshift/descheduler/blame/master/pkg/descheduler/strategy_migration.go#L215 <-- this line is the problem I have a working PR with the Fix