Exception Request for VEP #371 - KubeVirt Integration Test Framework

[Lee Yarwood]

Hello all,

I'd like to request a VEP freeze exception for VEP #371, KubeVirt Integration Test Framework (owning SIG: control-plane).

- Tracking issue: https://github.com/kubevirt/enhancements/issues/371
- VEP PR: https://github.com/kubevirt/enhancements/pull/348
- Target: Alpha in v1.10.0

1. Justification
The VEP PR is effectively ready to merge and has broad support, it currently carries /lgtm from @jschintag and @0xFelix, and earlier change requests (from @EdDev and others) have been addressed. A working proof of concept already exists across kubevirt/kubevirt#18726–#18731 (20 passing tests across 8 categories, including an instancetype-upgrade suite migrated from functional tests with a ~13.4x speedup). The only outstanding item is final review closure and merge, which slipped past the freeze by a matter of days.

2. Additional time requested
One week from the freeze date to obtain the remaining approval and merge the VEP PR.

3. Impact if not granted
Slipping to the next cycle delays a piece of shared testing infrastructure that other VEPs and contributors are already positioned to build on (faster, cluster-free integration coverage for controller/API changes, and CRD schema-evolution validation relevant to skip-level upgrades, e.g. VEP #309). The PoC would remain un-upstreamed for a full release with no offsetting benefit, given that the design is already agreed upon.

Regards,

Lee

[Lee Yarwood]

This has merged and can be ignored.

Cheers,

Lee