[
https://issues.apache.org/jira/browse/YUNIKORN-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767169#comment-17767169
]
Craig Condit commented on YUNIKORN-1941:
----------------------------------------
IMO, this makes more sense as a standalone webhook (apart from YuniKorn).
Segregating workloads to a specific subset of a cluster is really not a
YuniKorn-specific feature. Kubernetes already supports this via nodeSelector,
etc. and you could enforce this in an admission controller separately from
YuniKorn and have it work with all workloads, not just those scheduled via
YuniKorn.
> 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]
