You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2022/11/14 14:59:00 UTC
[jira] [Resolved] (YUNIKORN-1374) [shim] use the parent's user-group info if the pod has an ownerReference defined
[ https://issues.apache.org/jira/browse/YUNIKORN-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko resolved YUNIKORN-1374.
------------------------------------
Resolution: Won't Do
Closing this as Won't do, because the current implementation works as intended.
> [shim] use the parent's user-group info if the pod has an ownerReference defined
> --------------------------------------------------------------------------------
>
> Key: YUNIKORN-1374
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1374
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: shim - kubernetes
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
>
> Certain workloads submit further pods from within the cluster.
> For example, the driver pod startved by {{spark-submit}} belongs to the user who authenticated externally. Subsequent executor pods, however, will be started by the driver pod from a service account which is defined in the command line.
> In order to properly track resource usage, we need to check if there is {{OwnerReference}} set for a given pod. If it is, then we need to look up the existing pod/application and replace the user and group info. This also ensures that placeholders are handled properly, too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org