rancher/plugins
1
0
Fork 1
mirror of https://github.com/rancher/plugins.git synced 2025-07-08 12:45:19 +00:00
Code Issues Projects Releases Wiki Activity
k3s has removed some standard plugins, which we need. So fork and add it back.
1,556 Commits 17 Branches 66 Tags 23 MiB
Go 99.7%
Shell 0.3%
6b30e290d2
Go to file
Emily Shepherd 6b30e290d2
Update portmap test's iptables error check 
GitHub Actions recently updated ubuntu-latest to 22.04 [1], which now
defaults to nfttables (rather than iptables-legacy) [2]. The portmap
tests in this project are written with the expectation that expected
error message for one test is in the iptables-legacy format.

This commit updates the check to make it work for both the
iptables-legecy and iptables-nftables variants.

References:
[1]: 4aba37bd3b
[2]: https://ubuntu.com/blog/whats-new-in-security-for-ubuntu-22-04-lts

Signed-off-by: Emily Shepherd <emily@redcoat.dev>
2022-12-06 18:56:59 +00:00
.github Merge pull request #740 from jpsim/patch-1 2022-05-04 11:00:26 -05:00
integration Replace nc with the local echo client. 2020-10-07 20:13:24 +02:00
pkg V2 API support for win-overlay CNI 2022-04-14 12:44:49 -04:00
plugins Update portmap test's iptables error check 2022-12-06 18:56:59 +00:00
scripts build: support riscv64 2022-04-29 01:53:59 +09:00
vendor Update github.com/vishvananda/netlink to v1.2.0-beta 2022-04-27 10:58:34 +09:00
.gitignore Update Vendor 2018-09-21 00:34:07 +08:00
build_linux.sh Add github build & test actions 2020-12-09 17:46:25 +01:00
build_windows.sh Add github build & test actions 2020-12-09 17:46:25 +01: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 Update github.com/vishvananda/netlink to v1.2.0-beta 2022-04-27 10:58:34 +09:00
go.sum Update github.com/vishvananda/netlink to v1.2.0-beta 2022-04-27 10:58:34 +09:00
LICENSE Initial commit 2017-03-10 16:46:52 +01:00
OWNERS.md Remove Bryan Boreham as maintainer 2021-05-21 13:13:36 +00: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 Add github build & test actions 2020-12-09 17:46:25 +01:00
test_windows.sh Add github build & test actions 2020-12-09 17:46:25 +01:00

README.md

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.