decouple klog and event recorder from the main flow

[sanposhiho]

scheduler_perf shows the latency drop when the guests use logs and event recording. Currently, we send logs and events from guests to hosts synchronously, but actually we can accept the delay in logging and event recording actually.

Probably we just keep logs and events in the guest's side when klog / event recorder is used and ship them to the host once the main function finishes. (goroutine isn't an option, wasm doesn't support it)

/kind feature

[k8s-triage-robot]

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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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]

/remove-lifecycle stale