koord-scheduler: support force sync data from informer

[eahydra]

Signed-off-by: Joseph joseph.t.lee@outlook.com

Ⅰ. Describe what this PR does

Currently, the existing scheduling plugins of koord-scheduler will construct the internal state data of the plugin based on the data in the Informer, such as which Pods are maintained in NodeNUMAResource and which CPUs are allocated, which Pods are maintained in DeviceShare and which GPU instances are allocated, and so on. These data must be correct, otherwise it may cause problems with the resources allocated during Pod scheduling, or the orchestration results may not meet expectations, which will seriously affect the runtime problems or availability of workloads.

In the current existing code, the EventHandler is registered with the Informer, and the internal state can be constructed after WaitForCacheSync returns, but WaitForCacheSync only means that the data queried from the APIServer is synchronized to the Store inside the Informer, and does not perceive the Event in the EventHandler whether processing is complete. This also means that when WaitForCacheSync returns, EventHandler may not have finished processing the existing Add Event, and this problem will be more obvious in a larger cluster.

Therefore, we need a mechanism that can help the plugin to correctly convert the data in the Informer to the internal state of the plugin, and ensure that subsequent Add/Update/Delete Events can be processed correctly. Hence the introduction of ForceSyncedEventHandler.

When the plugin is initialized, you can register the EventHandler through frameworkexthelp.ForceSyncFromInformer. This function will automatically start the Informer, and wait for the data to be synchronized successfully before pouring the current data into the EventHandler.

[codecov]

Codecov Report

Base: 67.93% // Head: 67.93% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (b7f2eba) compared to base (9ff814a).
Patch coverage: 85.71% of modified lines in pull request are covered.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #830   +/-   ##
=======================================
  Coverage   67.93%   67.93%           
=======================================
  Files         216      217    +1     
  Lines       24381    24432   +51     
=======================================
+ Hits        16564    16599   +35     
- Misses       6668     6685   +17     
+ Partials     1149     1148    -1     

Flag	Coverage Δ
unittests	67.93% <85.71%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...r/plugins/elasticquota/core/group_quota_manager.go	72.67% <0.00%> (-0.60%)	⬇️
.../scheduler/plugins/elasticquota/core/quota_info.go	82.11% <16.66%> (-1.71%)	⬇️
pkg/scheduler/plugins/deviceshare/device_cache.go	86.21% <82.75%> (-0.36%)	⬇️
...heduler/frameworkext/helper/synced_eventhandler.go	83.63% <83.63%> (ø)
pkg/scheduler/plugins/coscheduling/core/core.go	40.13% <100.00%> (+0.82%)	⬆️
pkg/scheduler/plugins/coscheduling/coscheduling.go	58.97% <100.00%> (-3.24%)	⬇️
...kg/scheduler/plugins/deviceshare/device_handler.go	100.00% <100.00%> (+7.93%)	⬆️
pkg/scheduler/plugins/deviceshare/plugin.go	88.81% <100.00%> (-1.24%)	⬇️
pkg/scheduler/plugins/deviceshare/pod_handler.go	95.18% <100.00%> (+0.58%)	⬆️
pkg/scheduler/plugins/elasticquota/node_handler.go	67.18% <100.00%> (-1.00%)	⬇️
... and 10 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[eahydra]

Discussion from kubernetes kubernetes/kubernetes#113763

[buptcozy]

/ltgm

[buptcozy]

/approve

[koordinator-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: buptcozy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• pkg/scheduler/OWNERS [buptcozy]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ZiMengSheng]

/lgtm

[FillZpp]

/milestone v1.1