[
https://issues.apache.org/jira/browse/YUNIKORN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076979#comment-17076979
]
Weiwei Yang commented on YUNIKORN-68:
-------------------------------------
Hi [~kmarton]
In this case, I don't see an option that we can get this work.
Let's live with it, maybe it is a good idea to add a NOTE message in our readme
to say that once the admission-controller is started, all new pods will be
scheduled by yunikorn.
> YuniKorn admission-controller should skip pods that explicitly set
> schedulerName
> --------------------------------------------------------------------------------
>
> Key: YUNIKORN-68
> URL: https://issues.apache.org/jira/browse/YUNIKORN-68
> Project: Apache YuniKorn
> Issue Type: Bug
> Reporter: Kinga Marton
> Assignee: Kinga Marton
> Priority: Major
>
> Currently, as long as the admission-controller is enabled, it will mutate the
> pod's spec and set schedulerName to Yunikorn no matter what. But in case some
> user wants to leverage default scheduler, and they set schedulerName
> explicitly, we should let it be that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
