Goal

Enable CNI partners to certify that their CNI works correctly with KubeVirt when using a non-masquerade network binding. By adding a configurable binding parameter to the existing Sonobuoy conformance suite and defining the process, partners can independently validate and certify their binding.

User Stories

• As a CNI partner, I want to run KubeVirt conformance tests with my network binding, so that I can certify my CNI for use with OpenShift Virtualization beyond the default masquerade binding.
• As a CNI partner, I want a documented certification process, so that I know what is required to certify my binding and can self-validate before submitting.

Non-Requirements

• MTV integration — MTV respecting the configured default binding is tracked separately.
• OpenShift UI integration — surfacing and selecting non-masquerade bindings in the UI is tracked separately.
• Prescribing specific benefits (IP persistence, direct addressability, etc.) — the vendor defines what their binding provides; certification validates conformance, not specific behaviors.
• New test cases — this uses the existing KubeVirt conformance test suite, parameterized with a binding flag, not a new custom test harness.

Notes

• The binding parameter should be added in tests/flags/flags.go and wired into tests/conformance/conformance.go so that VM specs in conformance tests use the configured binding instead of masquerade.
• Partners run the standard Sonobuoy conformance suite with the binding parameter set to their binding type — no separate tooling is needed.
• Stakeholder alignment with the Certification team and Support team is a prerequisite before the first partner can be certified.