[
https://issues.apache.org/jira/browse/YUNIKORN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523201#comment-17523201
]
Chaoran Yu commented on YUNIKORN-966:
-------------------------------------
Hi [~steinsgateted], to make sure I understand your question, are you saying
that the code is already behaving as expected without implementing this JIRA?
My original thinking was to deal with cases when the Spark pods have a user
label that's in conflict with the user label on the SparkApp CRD objects, or
when the Spark pods don't have a user label at all. In both cases, the user
label on the CRD, if there's one, should take precedence
> Retrieve the username from the SparkApp CRD
> -------------------------------------------
>
> Key: YUNIKORN-966
> URL: https://issues.apache.org/jira/browse/YUNIKORN-966
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: shim - kubernetes
> Reporter: Chaoran Yu
> Assignee: ted
> Priority: Minor
>
> Currently the shim only looks at the pods to get the value of the label
> yunikorn.apache.org/username. When the Spark operator plugin is enabled, we
> should look at the SparkApp CRD for the label.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
