Change Details

We have some projects on gitlab (liberica, tcp-mss-clamper, ipip-multiqueue-optiimizer) that have some unique requirements: * Load eBPF programs on kernel * Be able to test traffic from a LB acting kernel to realservers This could potentially trigger severe networking issues on gitlab runners. As mentioned by @BCornwall it looks like we could leverage https://docs.gitlab.com/runner/executors/custom.html and spawn VMs using libvirt (https://docs.gitlab.com/runner/executors/custom_examples/libvirt.html)

We have some projects on gitlab (liberica, tcp-mss-clamper, ipip-multiqueue-optiimizer) that have some unique CI/testing requirements: * Load eBPF programs on kernel * Be able to test traffic from a LB acting kernel to realservers This could potentially trigger severe networking issues on gitlab runners. As mentioned by @BCornwall it looks like we could leverage https://docs.gitlab.com/runner/executors/custom.html and spawn VMs using libvirt (https://docs.gitlab.com/runner/executors/custom_examples/libvirt.html)

We have some projects on gitlab (liberica, tcp-mss-clamper, ipip-multiqueue-optiimizer) that have some unique CI/testing requirements: * Load eBPF programs on kernel * Be able to test traffic from a LB acting kernel to realservers This could potentially trigger severe networking issues on gitlab runners. As mentioned by @BCornwall it looks like we could leverage https://docs.gitlab.com/runner/executors/custom.html and spawn VMs using libvirt (https://docs.gitlab.com/runner/executors/custom_examples/libvirt.html)