[
https://issues.apache.org/jira/browse/YUNIKORN-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg closed YUNIKORN-16.
-----------------------------------------
Fix Version/s: 0.8
Resolution: Fixed
All subtasks are done closing this as implemented
> Support co-exist with other Kubernetes schedulers
> -------------------------------------------------
>
> Key: YUNIKORN-16
> URL: https://issues.apache.org/jira/browse/YUNIKORN-16
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: shim - kubernetes
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
> # Disable default scheduler and just run YuniKorn.
> # Run both default scheduler and YuniKorn, but each manages a dedicated set
> of nodes.
> # 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
