[
https://issues.apache.org/jira/browse/YUNIKORN-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760282#comment-17760282
]
Marc Singer commented on YUNIKORN-1941:
---------------------------------------
[~ccondit] what would be the best way to accomplish this behavior? We have our
own custom admission webhook, but I am refraining from adding toleration to
pods with scheduler: Yunikorn (we are using Plugin-Mode), because I don't
understand the impact of this interaction.
Also I noticed when Yunikorn runs on our cluster, it correctly reports the full
clusters resources (capacity - occupation), but for monitoring it would be
better if Yunikorn supported the limitation of nodes natively and only reported
the capacity / utilization of the nodes that are labeled / tainted / annotated.
About Autoscaler I have limited experience. Does it work outside of the
limitations of the scheduler?
> 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]
