Skip to content

Add the tap and vrf plugins in doc #127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
astraw99 wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −0
Open

Add the tap and vrf plugins in doc #127

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/plugins/current/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ These are general-purpose CNI network plugins maintained by the containernetwork
* [`ptp`](main/ptp): Creates a veth pair
* [`host-device`](main/host-device): Moves an already-existing device into a container
* [`vlan`](main/vlan): Creates a vlan interface off a master
* [`tap`](main/tap): Creates a tap device inside the container namespace

#### Windows: windows specific

Expand All @@ -38,6 +39,7 @@ These are general-purpose CNI network plugins maintained by the containernetwork
* [`bandwidth`](meta/bandwidth): Allows bandwidth-limiting through use of traffic control tbf (ingress/egress)
* [`sbr`](meta/sbr): A plugin that configures source based routing for an interface (from which it is chained)
* [`firewall`](meta/firewall): A firewall plugin which uses iptables or firewalld to add rules to allow traffic to/from the container
* [`vrf`](meta/vrf): Creates a [VRF](https://www.kernel.org/doc/Documentation/networking/vrf.txt) in the network namespace

## Contact

Expand Down