Configmaps werent correctly configured, because the api group was wrongly setup and generated code was faulty

switches created by the voerlay were having issues being deployed as the volume wasnt correctly set up

switch ipv6 addresses where buggy, and where having assigned a non compliant ipv6. now implemented some unit tests plus fixed this error

added managing role for this multus crds

NetAttachDefs resources from multus now are created with the overlay, using the specified number inside the spec. By default it's still defined to 10 interfaces

    Following up an issue where the controller manager couldnt create required components

Following up an issue where the controller manager couldnt create required components

Makefile wasnt separating the temporal resources from the rest of the deployment, leading to a yaml reading issue when deploying the app

l2sm nemo version doesnt support vlinks

Development

in following commits, network attachment definitions are going to be intrinsecally deployed with the network overlay.