[jira] [Commented] (YUNIKORN-2791) [Umbrella] Tracking non-Yunikorn allocations in the core

["Craig Condit (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YUNIKORN-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890545#comment-17890545 ] 

Craig Condit commented on YUNIKORN-2791:
----------------------------------------

This is all shaping up nicely. One suggestion: I've been looking at the full state dump now that the feature is active, and it seems to me that we should populate allocationTags for foreign allocations as well. This makes things like pod name and other metadata available. Especially once we do the web UI changes to expose this information, we're going to want it.

> [Umbrella] Tracking non-Yunikorn allocations in the core
> --------------------------------------------------------
>
>                 Key: YUNIKORN-2791
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2791
>             Project: Apache YuniKorn
>          Issue Type: New Feature
>          Components: core - scheduler, scheduler-interface, shim - kubernetes
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>              Labels: release-notes
>
> Currently, we don't know what non-YK pods are assigned to a particular node in the core. We only track the total amount of allocations as {{occupiedResources}} object inside the {{objects.Node}} type. If the tracking somehow becomes out of sync with the actual cluster state, it's very difficult to know what went wrong, because these allocations are not shown in the state dump.
> In order to enhance supportability, we want to track all non-YK pods per node on the core side.



--
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