k3s has removed some standard plugins, which we need. So fork and add it back.
Go to file
Casey Callendrello e5df283ab3
ci, go.mod: bump to go 1.23 (#1094)
* ci, go.mod: bump to go 1.23

Now that go.mod matches our go version, we can stop setting go version
in CI separately.

Signed-off-by: Casey Callendrello <c1@caseyc.net>

* minor: fix lint errors

Bumping golangci-lint to v1.61 introduced some new reasonable checks;
fix the errors they found.

Signed-off-by: Casey Callendrello <c1@caseyc.net>

* ci: bump golangci-lint to v1.61.0

Also, fix some deprecated config directives.

Signed-off-by: Casey Callendrello <c1@caseyc.net>

---------

Signed-off-by: Casey Callendrello <c1@caseyc.net>
2024-09-17 12:28:55 +02:00
.github ci, go.mod: bump to go 1.23 (#1094) 2024-09-17 12:28:55 +02:00
integration bandwidth: possibility to exclude some subnets from traffic shaping 2024-04-08 15:39:46 +09:00
pkg ci, go.mod: bump to go 1.23 (#1094) 2024-09-17 12:28:55 +02:00
plugins ci, go.mod: bump to go 1.23 (#1094) 2024-09-17 12:28:55 +02:00
scripts Update to Go v1.22 in CI and release 2024-03-11 15:52:12 +01:00
vendor Vendor nftables library, add utils.SupportsIPTables and utils.SupportsNFTables 2024-09-16 21:17:49 +02:00
.gitignore Update Vendor 2018-09-21 00:34:07 +08:00
.golangci.yml ci, go.mod: bump to go 1.23 (#1094) 2024-09-17 12:28:55 +02:00
.yamllint.yml ci(lint): setup yamllint linter 2023-02-25 12:10:11 +00:00
build_linux.sh build: Use POSIX sh for shell scripts 2023-09-29 16:57:19 +02:00
build_windows.sh build: Use POSIX sh for shell scripts 2023-09-29 16:57:19 +02:00
CONTRIBUTING.md Merge pull request #396 from oshothebig/contributing-doc 2019-10-09 10:21:03 -05:00
DCO Add missing DCO 2018-10-11 16:15:24 +01:00
go.mod ci, go.mod: bump to go 1.23 (#1094) 2024-09-17 12:28:55 +02:00
go.sum Vendor nftables library, add utils.SupportsIPTables and utils.SupportsNFTables 2024-09-16 21:17:49 +02:00
LICENSE Initial commit 2017-03-10 16:46:52 +01:00
OWNERS.md Update email to gmail 2022-12-07 11:57:16 -07:00
README.md dummy: Create a Dummy CNI plugin that creates a virtual interface. 2022-08-11 13:50:37 +01:00
RELEASING.md Add release process 2017-07-11 13:57:49 -07:00
test_linux.sh build: Use POSIX sh for shell scripts 2023-09-29 16:57:19 +02:00
test_windows.sh build: Use POSIX sh for shell scripts 2023-09-29 16:57:19 +02:00

test

Plugins

Some CNI network plugins, maintained by the containernetworking team. For more information, see the CNI website.

Read CONTRIBUTING for build and test instructions.

Plugins supplied:

Main: interface-creating

  • bridge: Creates a bridge, adds the host and the container to it.
  • ipvlan: Adds an ipvlan interface in the container.
  • loopback: Set the state of loopback interface to up.
  • macvlan: Creates a new MAC address, forwards all traffic to that to the container.
  • ptp: Creates a veth pair.
  • vlan: Allocates a vlan device.
  • host-device: Move an already-existing device into a container.
  • dummy: Creates a new Dummy device in the container.

Windows: Windows specific

  • win-bridge: Creates a bridge, adds the host and the container to it.
  • win-overlay: Creates an overlay interface to the container.

IPAM: IP address allocation

  • dhcp: Runs a daemon on the host to make DHCP requests on behalf of the container
  • host-local: Maintains a local database of allocated IPs
  • static: Allocate a single static IPv4/IPv6 address to container. It's useful in debugging purpose.

Meta: other plugins

  • tuning: Tweaks sysctl parameters of an existing interface
  • portmap: An iptables-based portmapping plugin. Maps ports from the host's address space to the container.
  • bandwidth: Allows bandwidth-limiting through use of traffic control tbf (ingress/egress).
  • sbr: A plugin that configures source based routing for an interface (from which it is chained).
  • firewall: A firewall plugin which uses iptables or firewalld to add rules to allow traffic to/from the container.

Sample

The sample plugin provides an example for building your own plugin.

Contact

For any questions about CNI, please reach out via:

If you have a security issue to report, please do so privately to the email addresses listed in the OWNERS file.