Skip to content

Commit

Permalink
docs: Update directory and change kata_tap0 to tap0_kata
Browse files Browse the repository at this point in the history
Update directory about state and tap device's should be tap0_kata for architecture.md

Fixes: kata-containers#736

Signed-off-by: duanquanfeng <duanquanfeng_yewu@cmss.chinamobile.com>
  • Loading branch information
frostmourner committed Sep 18, 2020
1 parent 72dcf4f commit 137d122
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions design/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@
* [exec](#exec)
* [kill](#kill)
* [delete](#delete)
* [state](#state)
* [Proxy](#proxy)
* [Shim](#shim)
* [Networking](#networking)
Expand Down Expand Up @@ -397,9 +398,9 @@ interfaces with `TAP` ones using Traffic Control:

With TC filter in place, a redirection is created between the container network and the
virtual machine. As an example, the CNI may create a device, `eth0`, in the container's network
namespace, which is a VETH device. Kata Containers will create a tap device for the VM, `kata_tap0`,
and setup a TC redirection filter to mirror traffic from `eth0`'s ingress to `kata_tap0`'s egress,
and a second to mirror traffic from `kata_tap0`'s ingress to `eth0`'s egress.
namespace, which is a VETH device. Kata Containers will create a tap device for the VM, `tap0_kata`,
and setup a TC redirection filter to mirror traffic from `eth0`'s ingress to `tap0_kata`'s egress,
and a second to mirror traffic from `tap0_kata`'s ingress to `eth0`'s egress.

Kata maintains support for MACVTAP, which was an earlier implementation used in Kata. TC-filter
is the default because it allows for simpler configuration, better CNI plugin compatibility, and performance
Expand Down

0 comments on commit 137d122

Please # to comment.