[jira] [Commented] (YUNIKORN-431) Submitting pods with non-existing queue name

["Wilfred Spiegelenburg (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YUNIKORN-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205939#comment-17205939 ] 

Wilfred Spiegelenburg commented on YUNIKORN-431:
------------------------------------------------

This is the correct approach. You should not provide a specific queue for a pod. The application when it gets created will provide the queue. Everything is linked to the application and its queue. 
If the application creation is linked to the CRD then the CRD is the place to provide the queue. If the pod and CRD are out of sync then that is a problem that needs to be solved by the submitter. Allowing multiple queues is not possible. We can also not make a choice at the scheduler level which queue to use. 

The scheduler will ignore the queue set on a specific ask (which is the representation of a pod in the core). That has been the case since we started. Otherwise you would be able to create an application in one queue and the pods that make up the application in other queues. Quotas would break as an example if we would allow that. An application will only be scheduled as part of one queue.

Placement rules might also play a role in the queue set for the app. However that is still linked to the app creation and would only affect the app queue and nothing else.

> Submitting pods with non-existing queue name
> --------------------------------------------
>
>                 Key: YUNIKORN-431
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-431
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>            Reporter: Kinga Marton
>            Priority: Major
>
> When we submit the CRD with let's say queueName=root.default, then we submit the pods linked to this application with queueName=root.xyz, where xyz is not an existing queue. The pod will be placed into queue root.default defined in the CRD, what is not the right approach
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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