57b42a7b99
Move the windows plugin to use the Host Compute (v2) APIs, as well as clean-up the code. Allows win-bridge to use either the old API or Host Compute (v2) api depending on a conf parameter. Fixes a leaked endpoint issue on windows for the v1 flow, and removes the hns/pkg from the linux test run.
win-bridge plugin
Overview
With win-bridge plugin, all containers (on the same host) are plugged into an L2Bridge network that has one endpoint in the host namespace.
Example configuration
{
"name": "mynet",
"type": "win-bridge",
"ipMasqNetwork": "10.244.0.0/16",
"ipam": {
"type": "host-local",
"subnet": "10.10.0.0/16"
}
}
Network configuration reference
name(string, required): the name of the network.type(string, required): "win-bridge".ipMasqNetwork(string, optional): setup NAT if not empty.ipam(dictionary, required): IPAM configuration to be used for this network.