[
https://issues.apache.org/jira/browse/YUNIKORN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093731#comment-17093731
]
Weiwei Yang commented on YUNIKORN-55:
-------------------------------------
Hi [~adam.antal]
{quote}
but at the point when we ask the scheduler for allocation we don't have an
existing pod, thus pod name - I don't know how could we simply inform the
scheduler about this.
{quote}
When we ask for the allocation, the pod is already created (this is triggered
when a pod is added to k8s). So we should be able to get pod spec info, such as
pod name, namespace, labels, and annotations. See more in
[https://github.com/apache/incubator-yunikorn-k8shim/blob/23e3f084d708096a90f54bfc969c3a9f08975fac/pkg/cache/context.go#L495.]
Can we get this info and put them into tags of AllocationAsk so they can be
carried over to the scheduler-core?
> Add pod labels and annotations to allocation ask attributes
> -----------------------------------------------------------
>
> Key: YUNIKORN-55
> URL: https://issues.apache.org/jira/browse/YUNIKORN-55
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler, shim - kubernetes, webapp
> Reporter: Weiwei Yang
> Assignee: Adam Antal
> Priority: Major
> Time Spent: 0.6h
> Remaining Estimate: 3.5h
>
> In YUNIKORN-54, we simplify the way to generate application IDs. The side
> effect is when we look at info from web UI, we lose some info about the pod
> info such as pod name, namespace, etc.
> A proper way to handle this is to get this info from pod and add labels,
> annotations info to allocation ask as attributes, and then send to
> scheduler-core. Also on web rest API, we need to display these attributes too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
