cache Node data via single unified Node data

[sanposhiho]

The Pod is cached in one scheduling cycle. https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/blob/main/guest/internal/cyclestate/cyclestate.go#L17-L19

And we can do the similar with Nodes.

There are currently two types for Nodes.

• nodeList in PreScore https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/blob/main/guest/prescore/prescore.go#L93
• nodeInfo in Filter https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/blob/main/guest/filter/filter.go#L81

We can unify them and cache Nodes as well like a Pod.

/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

[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