[YUNIKORN-16] Support co-exist with other Kubernetes schedulers

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.8
• Component/s: shim - kubernetes
• Labels: pull-request-available
• Target Version: 0.8
• Assignee: Weiwei Yang
• Reporter: Weiwei Yang
• Created: 04/Mar/20 10:38
• Updated: 27/Mar/20 12:32
• Resolved: 27/Mar/20 12:32

Description

Kubernetes supports to have multiple schedulers in one cluster. Actually, the simplest way to deploy YuniKorn is to co-exist with the default scheduler. Deployment mode has the following 3 options

1. Disable default scheduler and just run YuniKorn.
2. Run both default scheduler and YuniKorn, but each manages a dedicated set of nodes.
3. Run both default scheduler and Yunikorn, and they share cluster nodes.

there is no additional work to support option 1 (current method)

to support option 2, we only need some small effort, for example, we can leverage taints and tolerations to isolate some nodes for YuniKorn

for option 3, there is much more work to do, e.g how to handle shared resources.

Issue Links

• links to: GitHub Pull Request #86

Sub-Tasks

• Support node capacity update: Closed
• Add UPDATE action in order to report node resource updates: Closed
• K8shim should report occupied resources to scheduler core: Closed