Default to using bridge binding for kubevirt platform VMs #1050
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Unlike vanilla KubeVirt installs, Kubevirt installed by CNV defaults to using the masquerade network interface binding. That binding uses NAT with the pod network which makes all the KubeVirt hypershift tenant nodes look like they have the same IP address. The result is a non-functional cluster.
We didn't notice this at first because we were testing locally with a setup similar to minikube+kubevirt. Once we transitioned to testing OCP+CNV the issue was obvious.