You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support Gateway accelerated interface (Bypass port)
For host networking, external bridge acts as the input/output port
with Node IP configured on the bridge itself as a local port.
When hardware acceleration capable devices, like ConnectX or
Bluefield2 cards are used, pods can use hardware accelerated
Virtual Functions (VFs) or SubFunctions(SFs) as interfaces,
and fully offload all kubernetes traffic flows.
But for host networking pods or when the host itself is the traffic
endpoint, not all kubernetes flows are accelerated since current
CT infrastructure cannot offload CT flows where external bridge
is the in/out port.
To allow accelerated traffic flows for host networking, this patch
allows specifying a gateway accelerated interface via the
`--gateway-accelerated-interface` flag. This can either be a
switchdev VF or SF, connected to the external bridge and holding
the Node IP.
┌──────────┐
│ br-ext │
┌─────┴──┐ │ ┌──────────┐
│ eth0 │ │ │ br-int │
└─────┬──┘ │ │ │
│ X────X │
┌────────┐ ┌─────┴──┐ │ │ │
│ eth0v0 ├─────┤ eth0_0 │ │ │ │
└────────┘ └─────┬──┘ │ └──────────┘
NODE_IP │ │
└──────────┘
where, eth0v0 and eth0_0 are, for ex., VF and VF representor of eth0 uplink.
Note that used netdevice must be excluded from device plugin pools,
so it won't be used for workload pods.
This flag should be used mutually exclusive to the existing
gateway option `--gateway-interface` flag.
Signed-off-by: Hareesh Puthalath <[email protected]>
0 commit comments