On Dec 8, 2021, at 1:47 PM, Craig Condit (Jira) <[email protected]> wrote: > > Craig Condit created YUNIKORN-971: > ------------------------------------- > > Summary: Implement YuniKorn as a Kubernetes Scheduler Plugin > Key: YUNIKORN-971 > URL: https://issues.apache.org/jira/browse/YUNIKORN-971 > Project: Apache YuniKorn > Issue Type: New Feature > Components: shim - kubernetes > Attachments: YuniKorn as K8S Scheduler Plugin.pdf
All, Since this is a fairly large feature, I wanted to make sure we had proper visibility on the dev mailing list for this one. The intention here is to provide an alternative execution model for YuniKorn on Kubernetes which utilizes the K8S Scheduling Framework (see https://kubernetes.io/docs/concepts/scheduling-eviction/scheduling-framework/ <https://kubernetes.io/docs/concepts/scheduling-eviction/scheduling-framework/>). This will allow us to better match features and behavior with the upstream scheduler as well as allow us to bypass YuniKorn-specific scheduling functionality in certain cases (i.e. pods not marked with an applicationId). This feature should be considered experimental for now, and it does not affect the default build of YuniKorn. Please do try it out and let us know how it works for you. The hope is that we can provide it as a tech preview for the YuniKorn 1.0 release early in 2022. JIRA Issue: https://issues.apache.org/jira/browse/YUNIKORN-971 <https://issues.apache.org/jira/browse/YUNIKORN-971> Initial PR: https://github.com/apache/incubator-yunikorn-k8shim/pull/336 <https://github.com/apache/incubator-yunikorn-k8shim/pull/336> Thanks, Craig
