[YUNIKORN-1685] Preemption doesn't trigger if pod requests resources not mentioned in quota

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: core - scheduler
• Labels: pull-request-available
• Target Version: 1.3.0
• Assignee: Craig Condit
• Reporter: Craig Condit
• Created: 11/Apr/23 20:06
• Updated: 20/Jun/23 14:41
• Resolved: 11/Apr/23 20:55

Description

After YUNIKORN-1632 (which added pods=1 to all kubernetes pod requests), preemption no longer works. This seems to be due to the fitness function not taking into account unspecified resources.

Issue Links

• relates to: YUNIKORN-1632 Yunikorn fails to account for the max number of pods on a node
• links to: GitHub Pull Request #527