kube-scheduler-wasm-extension icon indicating copy to clipboard operation
kube-scheduler-wasm-extension copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Grow examples

Open sanposhiho opened this issue 1 year ago • 4 comments

We have a few examples only for very basic usecases. On the other hand, we have almost all the features the scheduling framework has. The scheduling framework is well created to cover wider usecases and so does our wasm extension.

Motivations:

  • Growing the variety of examples would be a great showcase for users who have different usecases.
  • By implementing some existing plugins in in-tree plugins, we can have a benchmark comparison between Golang plugin and wasm plugin via scheduler_perf.
  • Cover multiple practical scenarios in e2e tests.

sanposhiho avatar Jan 29 '24 01:01 sanposhiho

/cc @Gekko0114

sanposhiho avatar Jan 29 '24 01:01 sanposhiho

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

k8s-triage-robot avatar Apr 28 '24 01:04 k8s-triage-robot

/remove-lifecycle stale

sanposhiho avatar Apr 28 '24 12:04 sanposhiho

/priority next-release

sanposhiho avatar Jul 23 '24 06:07 sanposhiho

Hello all,

Thanks for creating such an interesting project!

I am a fellow Kubernetes contributor and I am interested in getting involved with this project.

I am interested in taking on one of the plugins from the https://github.com/kubernetes-sigs/scheduler-plugins and porting it to WASM.

Do you have any preference on which one?

dejanzele avatar Oct 18 '24 13:10 dejanzele

Hi @dejanzele. Thanks, feel free to create a PR and then ping me, @Gekko0114 and @utam0k.

Speaking of which, instead of sigs/scheduler-plugins, in-tree plugins should be priority now. I suggest nodeunschedulable as a starting point, which I believe we can implement it without any additional feature to the current SDK.

sanposhiho avatar Oct 19 '24 07:10 sanposhiho

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

k8s-triage-robot avatar Jan 17 '25 07:01 k8s-triage-robot

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/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 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

k8s-triage-robot avatar Feb 16 '25 08:02 k8s-triage-robot

Hi @sanposhiho. I would like to work on this issue. Do you have any recommendations on which in-tree plugins to work on?

unvavo avatar Feb 19 '25 14:02 unvavo

@unvavo Awesome, try seeing NodePorts, I guess that's also implementable already.

sanposhiho avatar Feb 22 '25 05:02 sanposhiho