Please note that the content of this page is currently WORK IN PROGRESS.
The controller is capable of supporting various inter-node mesh types, interface types, and connectivity options. Examples of mesh types are: vxlan mesh [cuurently], srv6, ipv4, ipv6, dot1q vlans [future]. Interface types such as memif, veth [current], and tap [future], and connectivity options are l2pp and l2mp.
The controller adapts dynamically to vnf to host changes. When K8s places a vnf on a host, the controller will adjust the configuration based on where the vnf is placed and how it relates to other vnfs in the vnf service definition.
See here for an expmple of a layer 2 point to point port chained vnf-service. The toplogy starts out by importing the yaml file where each vnf is on the same host. It then adapts to changes where the vnfs are placed on separate hosts.
See here for an example of a layer 2 point to multi-point port bridged vnf-service. The toplogy starts out by importing the yaml file where each vnf is on the same host. It then adapts to changes where the vnfs are placed on separate hosts.