You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2020/03/24 03:44:00 UTC

[jira] [Updated] (YUNIKORN-16) Support co-exist with other Kubernetes schedulers

     [ https://issues.apache.org/jira/browse/YUNIKORN-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Weiwei Yang updated YUNIKORN-16:
--------------------------------
    Target Version: 0.8

> 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
>            Priority: Major
>
> 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-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org