rancher/plugins
1
0
Fork 1
mirror of https://github.com/rancher/plugins.git synced 2025-07-07 12:10:20 +00:00
Code Issues Projects Releases Wiki Activity
k3s has removed some standard plugins, which we need. So fork and add it back.
1,671 Commits 17 Branches 66 Tags 23 MiB
Go 99.7%
Shell 0.3%
ca12d49b41
Go to file
Artur Korzeniewski ca12d49b41 Add routes propagation for VRF plugin 
Up until now, if previous plugin assigned routes to interface, movement of
this interface to new VRF cause routes to be deleted.

This patch adds funtionality to VRF plugin to save the routes before
interface is assgined to VRF, and then re-apply all saved routes to new VRF.

Signed-off-by: Artur Korzeniewski <artur.korzeniewski@travelping.com>
2023-06-02 14:21:28 +02:00
.github github: remove stale issue cleanup 2023-05-25 10:31:15 +02:00
integration enable govet and unparam linters 2023-04-11 12:07:04 +02:00
pkg Merge pull request #883 from mmorel-35/linter-2 2023-04-24 17:42:55 +02:00
plugins Add routes propagation for VRF plugin 2023-06-02 14:21:28 +02:00
scripts Bump to golang 1.20 to pick up go1.19.6 / go1.20.1 CVE fixes 2023-04-21 05:21:43 +00:00
vendor build(deps): bump github.com/Microsoft/hcsshim from 0.9.8 to 0.9.9 2023-05-01 03:02:09 +00:00
.gitignore Update Vendor 2018-09-21 00:34:07 +08:00
.golangci.yml enable govet and unparam linters 2023-04-11 12:07:04 +02:00
.yamllint.yml ci(lint): setup yamllint linter 2023-02-25 12:10:11 +00: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 build(deps): bump github.com/Microsoft/hcsshim from 0.9.8 to 0.9.9 2023-05-01 03:02:09 +00:00
go.sum build(deps): bump github.com/Microsoft/hcsshim from 0.9.8 to 0.9.9 2023-05-01 03:02:09 +00: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 remove govet and gofmt from test_linux.sh 2023-03-13 22:47:17 +00: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.