Copied Yossi's comment from the parent epic:

Programmatic skips that still exist in network tier-2 tests:
1.
tests/network/ovs_bond/test_bond_link_down.py
This module has one test, and it is specific for customer-0 setup.
As the customer-0 tests are marked with `ovs_brcnv` marker, they are not supposed to be executed anyway as long as the execution includes a marker filter (`-m`) which doesn't include this marker.
The skip is not directly in the test, but rather implicit in a fixture used by it (bond_and_privileged_pod).

2.
virtctl_expose_service (fixture in tests/network/general/test_ip_family_services.py)
The test that invokes this fixture is skipped when attempting to create a service of type `RequireDualStack` on a single-stack cluster.
My suggestion to replace the parameterization of the existing test with separating it do individual test, where one is dedicated to this service type, and marked with either
1 - a new `dual_stack` marker
2 - both `ipv4` and `ipv6` markers, which already exist.

3.
tests/network/nmstate/test_nmstate_management_iface.py
All 4 tests in this module are always skipped because they are destructive.
These tests alter the node's primary interface - either using it as port interface for a node bridge, or modify its IPv4 setting to test its affect on VMs connectivity (via the VM's primary interface).
None of this is no longer applicable - it is not allowed in OVN-k8s clusters (because the node's primary interface serves as a port for the default br-ex OVS bridge), and OVN-k8s remained the only supported CNI in openshift clusters (OpenshiftSDN is no longer supported).
Therefore - these tests can and should be removed (don't forget to also delete their polarion instances).