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

Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2022/12/12 02:26:00 UTC

[jira] [Resolved] (YUNIKORN-1398) Remove non daemonset reservation from node before allocating daemonset pod

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

Wilfred Spiegelenburg resolved YUNIKORN-1398.
---------------------------------------------
    Fix Version/s: 1.2.0
       Resolution: Fixed

Committed the change

> Remove non daemonset reservation from node before allocating daemonset pod
> --------------------------------------------------------------------------
>
>                 Key: YUNIKORN-1398
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1398
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>            Reporter: Manikandan R
>            Assignee: Manikandan R
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.2.0
>
>
> If we get a daemon set pod that needs to be scheduled we need to schedule that only on a specific node. If that node is reserved for anything but another daemon set pod the reservation should immediately be cancelled and the daemon set pod should take over the node reservation.
> This could happen during scale up with daemon set pods that are not critical and asks that have been outstanding for a while.



--
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