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 2026/05/01 02:42:00 UTC
[jira] [Commented] (YUNIKORN-3269) Kubernetes shim should respect node cordon state
[ https://issues.apache.org/jira/browse/YUNIKORN-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077472#comment-18077472 ]
Wilfred Spiegelenburg commented on YUNIKORN-3269:
-------------------------------------------------
[~jshmchenxi] I have added you to the list of contributors so you can assign jiras to yourself.
I have also started the build process on your PR.
It looks good so far. Thank you for your contribution.
> Kubernetes shim should respect node cordon state
> ------------------------------------------------
>
> Key: YUNIKORN-3269
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3269
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Xi Chen
> Assignee: Xi Chen
> Priority: Major
> Labels: pull-request-available
>
> YuniKorn’s Kubernetes shim does not fully preserve Kubernetes node cordon state when syncing nodes to scheduler-core.
> A Kubernetes node with spec.unschedulable=true should remain unavailable for scheduling in YuniKorn. Today, the shim registers nodes with scheduler-core and can restore them to schedulable state without checking Node.Spec.Unschedulable. The node update path also does not translate cordon/uncordon changes into corresponding scheduler-core drain/restore actions.
> This can make a Kubernetes SchedulingDisabled node appear schedulable to YuniKorn.
--
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