You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/07/11 17:46:00 UTC

[jira] [Resolved] (YUNIKORN-2703) Core: Fallback to default queue if no placement rules match

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

Craig Condit resolved YUNIKORN-2703.
------------------------------------
    Fix Version/s: 1.6.0
                   1.5.2
       Resolution: Fixed

Merged to master and backported (manually) to branch-1.5.

> Core: Fallback to default queue if no placement rules match
> -----------------------------------------------------------
>
>                 Key: YUNIKORN-2703
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2703
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>            Reporter: Mit Desai
>            Assignee: Mit Desai
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0, 1.5.2
>
>
> YUNIKORN-1650 added an override for default queue name in the config map to solve for the scenario where the provided placement rule is evaluated before other rules.
> Scheduler also adds a default queue if the pod labels or annotations does not define a queue name. Because this happens before the placement rules are evaluated, we end up in the same situation of applications getting placed in the default queue and ignoring all other placement rules.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org