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

Import scheduler_perf from Kubernetes repository rather than maintaining a copy

Open sanposhiho opened this issue 1 year ago • 15 comments

We have a performance test for our scheduler in https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/tree/main/internal/e2e/scheduler_perf.

The scheduler_perf is importable now, we no longer need to maintain the copy. https://github.com/kubernetes/kubernetes/pull/119079

/kind cleanup

sanposhiho avatar Jan 14 '24 04:01 sanposhiho

Can I give it a try?

utam0k avatar Jan 14 '24 12:01 utam0k

Yes, but we probably have to wait for a release of k/k?

sanposhiho avatar Jan 14 '24 12:01 sanposhiho

/assign @utam0k (but after v1.30)

sanposhiho avatar Feb 09 '24 02:02 sanposhiho

It's time to bump up to K1.30. I'm trying it...

utam0k avatar Apr 28 '24 07:04 utam0k

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 Jul 27 '24 07:07 k8s-triage-robot

/remove-lifecycle stale

sanposhiho avatar Jul 27 '24 09:07 sanposhiho

I am working on it, but it is taking time.

utam0k avatar Jul 28 '24 08:07 utam0k

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 Oct 26 '24 09:10 k8s-triage-robot

If it’s okay for it to take a little time, may I give it a try?

bells17 avatar Oct 30 '24 09:10 bells17

I'm ok, if @utam0k is ok to pass it over.

sanposhiho avatar Oct 30 '24 09:10 sanposhiho

Sure, please take it over. Updating k8s was difficult for me.

utam0k avatar Oct 30 '24 10:10 utam0k

/assign @bells17

sanposhiho avatar Oct 30 '24 11:10 sanposhiho

https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/pull/128 upgrades k/k.

/remove-lifecycle stale

sanposhiho avatar Nov 11 '24 16:11 sanposhiho

I spoke directly with @bells17 and took over this issue.

saku3 avatar Feb 08 '25 04:02 saku3

/unassign @bells17 /assign @saku3

sanposhiho avatar Feb 08 '25 06:02 sanposhiho