You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2023/05/24 15:59:00 UTC
[jira] [Resolved] (YUNIKORN-1745) Add implementation to MockedAPIProvider.AddEventHandler()
[ https://issues.apache.org/jira/browse/YUNIKORN-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko resolved YUNIKORN-1745.
------------------------------------
Fix Version/s: 1.3.0
Resolution: Fixed
> Add implementation to MockedAPIProvider.AddEventHandler()
> ---------------------------------------------------------
>
> Key: YUNIKORN-1745
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1745
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: shim - kubernetes, test - unit
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.3.0
>
>
> Currently, the implementation of MockedAPIProvider.AddEventHandler() is empty:
> {noformat}
> func (m *MockedAPIProvider) AddEventHandler(handlers *ResourceEventHandlers) {
> // no impl
> }
> {noformat}
> However, if we use {{MockScheduler}}, this method will eventually be called. If we save the handlers, we can simulate shared informers on a separate goroutine and we can send events for adding/updating/removing pods, nodes and config maps.
> It's also necessary to create PodEventHandler & register general.Manager in testing mode, so we can use it properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org