[SIG-Scale] v1.2 and v1.3 planning

kubevirt / kubevirt

Kubernetes Virtualization API and runtime in order to define and manage virtual machines.

https://kubevirt.io

Apache License 2.0

5.61k stars 1.33k forks source link

[SIG-Scale] v1.2 and v1.3 planning #10737

Closed rthallisey closed 3 months ago

rthallisey commented 11 months ago

v1.2

[ ] Simulate kubevirt's control-plane performance with kwok
- [x] https://github.com/kubevirt/kubevirt/issues/11128
- [x] https://github.com/kubevirt/kubevirt/issues/11129

v1.3

[ ] Add metrics for kubevirt control-plane mem/cpu usage
[ ] Report after each release kubevirt's control-plane mem/cpu usage
[ ] Add metrics to virt-launcher mem and cpu usage
[ ] Report after each release kubevirt's mem/cpu overhead
[ ] Reduce virt-launcher memory overhead

matthewei commented 11 months ago

can i do something for it?

rthallisey commented 11 months ago

@matthewei, yes. This list captures our goals at a high-level. If you want to work on one of these, create and issue outlining your approach and tag SIG-scale. We'll discuss in our weekly SIG-scale meetings the design and progress - https://calendar.google.com/calendar/u/0/embed?src=kubevirt@cncf.io

kubevirt-bot commented 6 months ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot commented 4 months ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

kubevirt-bot commented 3 months ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 3 months ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/kubevirt/issues/10737#issuecomment-2258971218): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.