An attempt to bump bridge-marker's cluster version to Kubernetes 1.34 failed on CI.

https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_bridge-marker/94/pull-bridge-marker-test/1971120741877288960

We will need to address this before OCP 4.21 goes out.

Kubernetes 1.34 (maps to OCP 4.21)

?

1. Reproduced on CI in https://github.com/kubevirt/bridge-marker/pull/94#issuecomment-3333272754
2.
3.

 • Failure [242.587 seconds]
bridge-marker
/tmp/bridgemarker/bridgemarker/tests/marker_test.go:35
  pod requiring bridge resource
  /tmp/bridgemarker/bridgemarker/tests/marker_test.go:75
    should be started only when bridge is available on node [It]
    /tmp/bridgemarker/bridgemarker/tests/marker_test.go:80
    Timed out after 240.004s.
    Expected
        <bool>: false
    to equal
        <bool>: true
    /tmp/bridgemarker/bridgemarker/tests/utils.go:157
------------------------------
./cluster/ssh.sh node01 -- sudo ip link add br_podtest type bridge
stdout: ...
, stderr selecting podman as container runtime
./cluster/ssh.sh node01 -- sudo ip link set br_podtest up
stdout: ...
, stderr selecting podman as container runtime
./cluster/ssh.sh node01 -- sudo ip link del br_podtest
stdout: ...
, stderr selecting podman as container runtime
JUnit report was created: /logs/artifacts/junit.functest.xml
Summarizing 1 Failure:
[Fail] bridge-marker pod requiring bridge resource [It] should be started only when bridge is available on node 
/tmp/bridgemarker/bridgemarker/tests/utils.go:157 

Success