kube-scheduler-simulator
kube-scheduler-simulator copied to clipboard
First release simulator/v0.1.0
/cc @adtac /cc @Huang-Wei /cc @alculquicondor /assign
Hello team. I'd like to release v0.1.0 after all bug-fix PRs are merged. So, PTAL when you are free. 🙇♂️
- [x] https://github.com/kubernetes-sigs/kube-scheduler-simulator/pull/18
- [x] https://github.com/kubernetes-sigs/kube-scheduler-simulator/pull/13
- [x] https://github.com/kubernetes-sigs/kube-scheduler-simulator/pull/9
- [x] https://github.com/kubernetes-sigs/kube-scheduler-simulator/pull/25
And, I also want to check if the image build by cloudbuild will work. So, we also have to wait for these PRs.
- [x] https://github.com/kubernetes-sigs/kube-scheduler-simulator/pull/21
- [x] https://github.com/kubernetes/test-infra/pull/23567
I saw the release guide for scheduler-plugins, and will follow the guide to release. https://github.com/kubernetes-sigs/scheduler-plugins/blob/master/doc/release-guide.md
And then, I'll create a release guide for the simulator. https://github.com/kubernetes-sigs/kube-scheduler-simulator/issues/19
Could you also expand the CONTRIBUTING.md
doc to guide developers? Like what are the main folders for, where are plugins located, etc.
I wonder if there should also be a way to run the simulator on a k8s cluster (as opposed to docker-compose). With the clarification that the UI wouldn't show what is running in the underlying cluster.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/triage accepted Not to mark as stale.
/retitle First release simulator/v0.1.0
I created priority/next-release tag, which shows what tasks should be done in next releases.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR 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 and PRs.
This bot triages issues and PRs 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 or PR as fresh with
/remove-lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten /lifecycle frozen
All priority/next-release are merged finally. I'm gonna release it soon.
🎉 🎉 🎉 🎉 🎉 🎉 🎉 https://github.com/kubernetes-sigs/kube-scheduler-simulator/releases/tag/simulator%2Fv0.1.0