RamLavi

> > Thanks @RamLavi for the exhausting analysis. I believe we exhausted all of our options. The order of the options matches my preference but here the option 1 needs...

[Change](https://github.com/kubevirt/community/compare/b2d541c0e6e788c62be411a93c28d235fc347f1f..063da916bb7c4ec985779014661bfeed324a4839): - updated the chosen the solution: validationAdmissionPolicy, following the positive feedback and POC done offline. - updated the backwards compatibility approach, and added an appendix to further discuss it....

> Thanks for the update Ram. > > @RamLavi please resolve all open conversations in this document in order to move forward. Technically speaking, I don't think I can resolve...

> Hey @vladikr! Before merging this, let's make sure we discuss all the points you've raised. > > > In general, the `ShadowNode` approach with the variation that @Barakmor1 suggested,...

when virt-controller creates the virt-launcher pod, the pod is caught by the kmp webhook for pods. It is then checked if it related to kubevirt vmi ([isRelatedToKubevirt()](https://github.com/k8snetworkplumbingwg/kubemacpool/blob/97e9201d0609d2f3ae7f23a68b4893f5961f2113/pkg/pool-manager/virtualmachine_pool.go#L326)) I think that...

seems like issue was introduced in [commit: bump kubvirt.io to v0.25.0](https://github.com/k8snetworkplumbingwg/kubemacpool/commit/d1cc39a4d13a3210f2723b4a38445e72a6707879)

Hey @machadovilaca Seems like `pull-kubevirt-e2e-k8s-1.30-sig-operator` lane is failing alot, can you check it out?

/retest

both docs are refactored in: https://github.com/ovn-org/ovn-kubernetes/pull/4537

/sig code-quality