components/ipam-ext: Remove primary-udn-kubevirt-binding NetworkAttachmentDefinition

[RamLavi]

What this PR does / why we need it:
passt is no longer the chosen kubevirt binding for primary UDN. Removing the deployment of the primary-udn-kubevirt-binding NetworkAttachmentDefinition accordingly.

Special notes for your reviewer:

Release note:

NONE

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from ramlavi. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[oshoval]

what about removing the ds please ?

[RamLavi]

That should be done on a separate PR.

[oshoval]

not mandatory imho, but ok if more comfortable for you
as long as the tests use managedTap before that, else they will fail

[RamLavi]

So perhaps it is better to do it on the PR that bumps ipam-ext?

[oshoval]

nope, orthogonal
passt can be removed after the tests are removed, this way we also each focus on orthogonal parts
as far as possible

flow should be adapt to managedTap,
green to remove passt all over

[oshoval]

lets please wait for ipam release and then add #1919
and just then remove passt
guess we are on the same page?

[RamLavi]

lets please wait for ipam release and then add #1919 and just then remove passt guess we are on the same page?

why is it on draft though?

[oshoval]

lets please wait for ipam release and then add #1919 and just then remove passt guess we are on the same page?

why is it on draft though?

just because didnt test it, need first the release

[kubevirt-bot]

@RamLavi: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-e2e-cluster-network-addons-operator-workflow-k8s	5fbf07a	link	true	/test pull-e2e-cluster-network-addons-operator-workflow-k8s

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.