[YUNIKORN-2083] Scheduler in standard mode should be able to handle pods with no applicationID defined

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: shim - kubernetes
• Labels: pull-request-available
• Target Version: 1.4.0
• Assignee: Craig Condit
• Reporter: Craig Condit
• Created: 27/Oct/23 20:43
• Updated: 20/Nov/23 16:42
• Resolved: 02/Nov/23 16:44

Description

The scheduler in plugin mode can handle the case where a Pod is defined with schedulerName: yunikorn but no applicationID set can still be scheduled; it is treated as a non-YuniKorn pod and passed through the default scheduler logic.

However, in the standard deployment mode we don't have any way to handle such pods, as there is no default scheduler embedded. Currently, these pods remain in Pending state but simply vanish from YuniKorn's perspective and are never scheduled, leading to subtle problems and difficult-to-diagnose issues.

It would be useful if these pods could be scheduled anyway, ideally using the same algorithm for applicationID generation that the admission controller uses. This would make standalone yunikorn more useful as a default scheduler replacement.

Issue Links

• links to: GitHub Pull Request #708