[
https://issues.apache.org/jira/browse/YUNIKORN-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-2100.
---------------------------------------------
Fix Version/s: 1.4.0
Resolution: Fixed
Changes committed, flow for pods through the informers is much easier to follow
and allows us to build new functionality for tracking non YuniKorn pods and
mutating resources for pods on top of.
> Merge functionality of node coordinator into context
> ----------------------------------------------------
>
> Key: YUNIKORN-2100
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2100
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: shim - kubernetes
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> In the kubernetes shim, we listen for pod events in multiple places.
> Specifically, the node coordinator is used to track updates to non-YuniKorn
> managed pods. However, this code always needs to update the context as well,
> so it makes more sense to combine this logic within the main Context's add /
> update / delete pod handlers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
