[
https://issues.apache.org/jira/browse/YUNIKORN-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040997#comment-18040997
]
Wilfred Spiegelenburg commented on YUNIKORN-2981:
-------------------------------------------------
This completely slipped from attention. Reviewed the last change that was made
and with a small change we can still get this into YuniKorn 1.8.
The previous comment gave the wrong default value. It should be *true* as we
need to preserve existing behaviour which is to override always. The rest stays
the same.
We do need a documentation update (YUNIKORN-3163) and release note (label
added).
> Support filtering schedulerName
> -------------------------------
>
> Key: YUNIKORN-2981
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2981
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: shim - kubernetes
> Reporter: haorenhui
> Assignee: Kaichia Chen
> Priority: Minor
> Labels: pull-request-available, release-notes
>
> In our K8S environment, there are multiple schedulers working
> simultaneously (provided by different vendors), and Yunikorn is currently
> unable to handle situations where pods in a certain namespace may need to be
> scheduled by different schedulers. The current approach is to intercept all
> pods in the namespace (enableYunikorn=true) and modify their schedularName.
> Regardless of whether its schedulerName value is default scheduler or other.
> We hope that Yunikorn can add process and bypassing of spec.schedulerName
> on pods in the configuration, just like namespace.
> {code:java}
> // case
> admissionController.filtering.processSchedulerNames:
> ^default-scheduler$|^yunikorn$
> admissionController.filtering.bypassSchedulerNames: ^other-scheduler$ {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
