[
https://issues.apache.org/jira/browse/YUNIKORN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868788#comment-17868788
]
Craig Condit commented on YUNIKORN-2768:
----------------------------------------
We really can't do something as expansive as matchers easily (the config syntax
required is beyond what configmaps support – i.e. simple key/value pairs).
However, it might be possible to have a configuration for a list of custom
labels (perhaps comma-separated) to consult to look for an application ID. I'd
probably prefer to see this only in the admission controller, so that the
canonical applicationID can be set properly before the scheduler sees the pod.
[~wilfreds], thoughts?
> Add support for AppID label selector instead of hardcoded label names
> ---------------------------------------------------------------------
>
> Key: YUNIKORN-2768
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2768
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Janek Bevendorff
> Priority: Major
>
> I find it kind of weird that the only way to set an AppID on my pods is via
> the {{applicationId}} label or the {{yunikorn.apache.org/app-id}} annotation,
> and (for some reason) the {{spark-app-selector}} label.
> Instead of hard-coding support for Spark (and only Spark), it'd be great if
> there were a general purpose {{matchLabels}} / {{matchExpressions}} label
> selector
> (https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#resources-that-support-set-based-requirements)
> for specifying which labels on a pod are treated as an application ID. This
> would alleviate the need for a hard-coded set of external labels for specific
> frameworks inside YuniKorn (such as {{spark-app-selector}}) and more flexibly
> allow me to properly schedule any kind of application, even if the
> application itself does not support YuniKorn as a scheduler.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
