[YUNIKORN-1562] plugin mode: remove status update completely

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: shim - kubernetes
• Labels: pull-request-available
• Target Version: 1.3.0
• Assignee: Wilfred Spiegelenburg
• Reporter: Wilfred Spiegelenburg
• Created: 07/Feb/23 04:37
• Updated: 20/Jun/23 14:41
• Resolved: 07/Feb/23 22:16

Description

The k8shim in plugin mode only updates the pod status to move the pod from the unschedulablePods structure to the activeQ. This caused an issue in the way we did it before YUNIKORN-1547 as we could leave a pod in a custom state that K8s does not know.

After YUNIKORN-1547 we used the pending state. There could still be cases that the state set by the plugin showed up and not the state that the pod was really in. A pod could be fully scheduled and running while still showing pending as set by the plugin.

The state change was added to the plugin code based on an incorrect assumption that it would trigger a move between the unschedulablePods and activeQ. However the scheduler explicitly excluded pod status when checking for updates. We should thus not set the status of the pod to limit side effects and impact.

Issue Links

• is related to: YUNIKORN-1547 Plugin mode shouldn't use nonstandard QuotaApproved status
• links to: GitHub Pull Request #522