[SIG-scale] Meeting Notes 2026-04-30
Andrew Burden
4/30/26
Recording: https://youtu.be/Vftj1olRq4Q
Attendees: rhallisey, fossedihelm
Agenda:
https://testgrid.k8s.io/kubevirt-presubmits#pull-kubevirt-e2e-k8s-1.34-sig-performance&width=20
This job is flaky
[alay, sreeja] Virt-handler traversing the process tree can take a long time if there are a lot of processes
File an issue
[vishnu] kube-burner job went through, unblocked on the kubeconfig issue. This PR is good to go: https://github.com/kubevirt/project-infra/pull/4703 . Need relevant tags, it's failing on an issue that is related to cluster cleanup (.i.e irrelevant to this PR). Can I get contributor access now, please? I want to be able to trigger tests myself. Let me know if I need to do something from my end in that regard, TIA.
Open a PR to add yourself as a contributor - https://github.com/kubevirt/project-infra/blob/main/github/ci/prow-deploy/kustom/base/configs/current/orgs/orgs.yaml#L20
2 people from the community will need to sponsor
[fossedihelm] k8s provider bump policy.
Quite all the other specific sig lanes use the latest provider
Bumped when the new provider becomes available and mandatory
Any concerns about doing the same for performance lane?
SIG-performance
Support a 1.34 lane until 1.34 is released
Create a second lane for 1.36 lane when kubevirt hits beta
Remove the 1.34 lane when kubevirt is released
[fossedihelm] https://github.com/kubevirt/kubevirt/pull/17435 do we want to perform some tests around this?
Any suggestions?