k8s-triage-robot
commented
2 months ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
sanposhiho
What would you like to be added:
EventHandler equivalent to notify updates to resources from host to wasm guest.
Why is this needed:
In current design, we passed nodes and pods to every wasm guest in every scheduling cycle. But, actually no need to pass nodes and pods every time since not all objects get changed between each scheduling cycle. We can always store every pod/node to all wasm guests' memory, and keep them up-to-date. Then, every wasm guest just needs to refer to those objects when needed, instead of getting them from host in every scheduling cycle, which requires overhead to marshall/unmarshall the objects.
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.