Import scheduler_perf from Kubernetes repository rather than maintaining a copy

kubernetes-sigs / kube-scheduler-wasm-extension

All the things to make the scheduler extendable with wasm.

Apache License 2.0

107 stars 22 forks source link

Import scheduler_perf from Kubernetes repository rather than maintaining a copy #94

Open sanposhiho opened 10 months ago

sanposhiho commented 10 months ago

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

utam0k commented 10 months ago

Can I give it a try?

sanposhiho commented 10 months ago

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

sanposhiho commented 9 months ago

/assign @utam0k (but after v1.30)

utam0k commented 6 months ago

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

k8s-triage-robot commented 3 months ago

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 commented 3 months ago

/remove-lifecycle stale

utam0k commented 3 months ago

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

k8s-triage-robot commented 2 weeks ago

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

bells17 commented 2 weeks ago

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

sanposhiho commented 2 weeks ago

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

utam0k commented 2 weeks ago

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

sanposhiho commented 2 weeks ago

/assign @bells17

sanposhiho commented 3 days ago

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

/remove-lifecycle stale