kube-scheduler-wasm-extension
kube-scheduler-wasm-extension copied to clipboard
Support `framework.Handle`
The scheduler exports framework.Handle to the plugins so that they can operate something on the framework side.
https://github.com/kubernetes/kubernetes/blob/add482a2d31db938f3dca87920313db9d1780cf5/pkg/scheduler/framework/interface.go#L601
Some functions don't need to be implemented though, we should support the common ones at least:
- [ ] SnapshotSharedLister
- [x] EventRecorder @Gekko0114 https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/pull/83
- [ ] RunFilterPluginsWithNominatedPods @chansuke
- [ ] GetWaitingPod @chansuke
- [x] RejectWaitingPod @Gekko0114 https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/pull/98
SnapshotSharedLister might not be needed if https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/issues/71 is complited, so lower priority for now.
I will work on EventRecorder
/assign @Gekko0114
@sanposhiho I would like to work on another one, do you have any recommendation? (which item has higher priority?)
I would say RunFilterPluginsWithNominatedPods is the one.
Thanks, then I will work on RunFilterPluginsWithNominatedPods next
Since RunFilterPlugins is complicated, I will work on RejectWaitingPod instead
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
/remove-lifecycle stale
@sanposhiho @Gekko0114 I would like to contribute to this issue. I'm interested in GetWaitingPod, but could you please share the priority and current status? :pray: Or any recommendations?
@chansuke This is just my impression, but I think GetWaitingPod is a good candidate because it's similar to rejectWaitingPod, which is already implemented. https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/pull/98/files
@Gekko0114 Thank you so much for your comment. I'll take a look.
/assign @chansuke
Thanks!
/assign
Will pick up SnapshotSharedLister.
/priority next-release
Not all, but at least, SnapshotSharedLister is.
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
/remove-lifecycle stale
@sanposhiho @Gekko0114
I'd like to work on RunFilterPluginsWithNominatedPods if no one is working.
@chansuke 👍
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
The Kubernetes project currently lacks enough active 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 rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten