In order to use the latest network-status annotation api, that among
else exposes pci-device information on sriov secondary nic, bumping
multus-client vendor to v1.3.0

Signed-off-by: Ram Lavi <ralavi@redhat.com>

Signed-off-by: Ram Lavi <ralavi@redhat.com>

Signed-off-by: Ram Lavi <ralavi@redhat.com>

Signed-off-by: Ram Lavi <ralavi@redhat.com>

The new package is used to give consistent names to networks and their
pod interfaces.
The primary network is using a pod interface name (eth0) that is defined
in this package and should be used by other packages for consistency.

Signed-off-by: Ram Lavi <ralavi@redhat.com>

There is a need to consolidate the pod-interface name scheme of networks
given in the VMI spec, so that they can be approached in consistent way
in different times in the VMI's lifecycle.
Introducing NameScheme that maps network names to
their appropriate network/pod interface name.

Signed-off-by: Ram Lavi <ralavi@redhat.com>

Create a map between SRIOV networks and their appropriate
PCI-Address, using the multus network-status annotation.

Signed-off-by: Ram Lavi <ralavi@redhat.com>

Patch the network-pci map to the annotation in virt-controller context,
if such map is created.
In addtion patch rbac is added to virt-controller.

Signed-off-by: Ram Lavi <ralavi@redhat.com>

Expose network-pci-map annotation using DownwardAPI feature [0].

[0] https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/

Signed-off-by: Ram Lavi <ralavi@redhat.com>

Utilize the SRIOV-network PCI-address mapping that was
digested from the multus network-status annotation and mounted to a
volume, in order to create the SRIOV devices.
If the map does not exist, then the mapping will fall back to the former
approach.

Solves issue [0] reported on flawed mapping of sriov on VMIs
with multiple SRIOV networks.

[0] kubevirt#7444

Signed-off-by: Ram Lavi <ralavi@redhat.com>

The new test added in order to check network-status annotation based
mapping of the networks to the appropriate PCI-Address - will
consistently pass only if the annotation exists and holds the pci-data.

In older versions of Multus the network-status annotation does not hold
the PCI-Address data (on version >=3.7 [0])

[0] https://github.com/k8snetworkplumbingwg/multus-cni/releases/tag/v3.7

Signed-off-by: Ram Lavi <ralavi@redhat.com>