The MetalLB E2E test suite can be run by creating a development cluster:
inv dev-env
and running the E2E tests against the development cluster:
inv e2etest
Run only BGP test suite:
inv e2etest --focus BGP
Run only L2 test suite:
inv e2etest --focus L2
The test suite will run the appropriate tests against the cluster.
Be sure to cleanup any previously created development clusters using inv dev-env-cleanup.
In order to test the multiple scenarios required for BGP, three different containers are required. The following diagram describes the network connectivity using the regular kind network, the pods and the containers involved.
┌────────────────────────────────────────────┐
│ exec network │
│ ┌─────────┐ │
│ │ │ │
│ │ Speaker ├────┐ ┌─────────────────┐ │
│ │ │ │ │ │ │
│ └─────────┘ │ │ ibgp-single-hop │ │
│ │ │ │ │
│ ┌─────────┐ │ └─────────────────┘ │
│ │ │ │ │
│ │ Speaker ├────┤ ┌───────────────────────┼──────────────────────────┐
│ │ │ │ │ │ │
│ └─────────┘ │ │ ┌─────────────────┐ │ ┌────────────────┐ │
│ │ │ │ │ │ │ │ │
│ ┌─────────┐ ├───┼──┤ ebgp-single-hop ├──┼───────┤ ibgp-multi-hop │ │
│ │ │ │ │ │ │ │ │ │ │
│ │ Speaker │ │ │ └─────────────────┘ │ └────────────────┘ │
│ │ ├────┘ │ │ │
│ └─────────┘ │ │ ┌────────────────┐ │
│ │ │ │ │ │
└────────────────────┼───────────────────────┘ │ ebgp-multi-hop │ │
│ │ │ │
│ multi-hop-net └────────────────┘ │
│ 172.30.0.0/16 │
│ fc00:f853:ccd:e798::/64 │
└──────────────────────────────────────────────────┘
The same layout is replicated to validate external routers reacheable via a VRF.
So, on top of what's described above, there is another set of 4 containers meant to be reached using an interface hosted inside a vrf created on the node:
┌─────────────────────┐
│ │
│ │
┌──┤ ibgp-vrf-multi-hop │
┌──────────────────────┐ │ │ │
│ │ │ │ │
│ │ │ └─────────────────────┘
┌───────────────────────┐ ┌──┤ ebgp-vrf-single-hop ├─────────────────────┤
│ │ │ │ │ │ ┌─────────────────────┐
│ │ │ │ │ vrf-multihop-net │ │ │
│ ┌─────────┐ │ │ └──────────────────────┘ │ │ │
│ │ │ ┌──────┤ │ └──┤ ebgp-vrf-multi-hop │
│ │ Speaker │ │ │ │ │ │
│ │ │ │ ───┼───────────────┤ │ │
│ └─────────┘ │ VRF│ vrf-net │ ┌──────────────────────┐ └─────────────────────┘
│ │ │ │ │ │
│ └──────┤ │ │ │
│ │ └──┤ ibgp-vrf-single-hop │
│ Node │ │ │
│ │ │ │
└───────────────────────┘ └──────────────────────┘
The above diagram is implemented in infra_setup.go.
The E2E tests can run while using existing FRR containers that act as the single/multi-hop BGP routers.
To do so, pass the flag external-containers with the value of a comma-separated list of containers names.
The valid names are: ibgp-single-hop / ibgp-multi-hop / ebgp-single-hop / ebgp-multi-hop.
The test setup will use them instead of creating the external frr containers on its own.
The requirements for this are:
- The external FRR containers must be named as
ibgp-single-hop/ibgp-multi-hop/ebgp-single-hop/ebgp-multi-hop. - When running with an multi-hop container, the
ebgp-single-hopcontainer must be present. Other than that, the multi-hop containers must be connected to a docker network namedmulti-hop-net. The test suite will take care of connecting theebgp-single-hopto the multi-hop-net and creating the required static routes between the speakers and the containers, as well as configuring the external FRR containers. - When using existing container, i.e.
ibgp_single_hop, you have to mount a directory namedibgp-single-hopthat has the initial frr configurations files (vtysh.conf, zebra.conf, daemons, bgpd.conf, bfdd.conf). Seemetallb/e2etest/config/frrfor example. Note that the test's teardown will delete the directory, so it's recommended to keep a copy of the directory in a different place.