You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/04/14 03:20:00 UTC
[jira] [Updated] (YUNIKORN-2981) Support filtering schedulerName
[ https://issues.apache.org/jira/browse/YUNIKORN-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated YUNIKORN-2981:
-------------------------------------
Labels: pull-request-available (was: )
> 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
>
> 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: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org