[
https://issues.apache.org/jira/browse/YUNIKORN-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759977#comment-17759977
]
Craig Condit commented on YUNIKORN-1941:
----------------------------------------
One thing to consider when implementing this is the impact it may have on the
cluster autoscaler. Normally (in an autoscaling environment) the autoscaler
kicks in when it sees unschedulable pods. However, if those pods appear to be
schedulable on a node which yunikorn is not using, this could interfere with
autoscaler behavior.
The normal Kubernetes way of restricting workloads is to use taints and
tolerations – i.e. taint nodes you want to prevent scheduling on, and tolerate
those taints only on the pods which should be allowed to schedule on them
anyway.
> Limit Yunikorn to only use certain nodes to schedule workloads
> --------------------------------------------------------------
>
> Key: YUNIKORN-1941
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1941
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Marc Singer
> Assignee: Marc Singer
> Priority: Major
>
> We want to limit Yunikorn to utilize a specific part of the Kubernetes
> cluster for it's workloads. These nodes should have a label or annotation
> that is configurable in the Yunikorn configuration and if present should
> limit workloads to only be scheduled on these specific nodes.
> According to the slack #dev channel, this should be accomplishable by
> limiting the nodes returned from the kubernetes-shim.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
