[
https://issues.apache.org/jira/browse/YUNIKORN-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633405#comment-17633405
]
Wilfred Spiegelenburg commented on YUNIKORN-1374:
-------------------------------------------------
The originator pod is the pod which defines the user details. There is no
support for running pods under the same application ID with different users. So
if the originator pod is handled all pods should be good. Owner references are
good for cleaning up pods using the garbage collector inside K8s. We only use
them for placeholders to make sure those get cleaned up when the originator pod
is cancelled.
Based on that I do not think we need to mess around with the owner references
for the usage tracking.
> [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: [email protected]
For additional commands, e-mail: [email protected]
