Casey Callendrello

Use non-privileged ICMP socket on Linux

7

Linux (and Darwin) support [non-privileged ICMP echo sockets][1]. It would be a fun exercise to use them, rather than requiring capabilities. [1]: https://lwn.net/Articles/420800/

Add v6 transport support for TCP and UDP.

3

Additionally, this supports url-style IP literals: v6 addresses must be surrounded by brackets. Signed-off-by: Casey Callendrello

CNI v0.5.2

6

WIP support for ConfigLists and multiple IPs TODO: fix kvm flannel nastiness.

Expose the `--raw-port` flag in the run and run-prepared subcommands

21

Fixes #2113

networking: refactor and split KVM logic

10

This hopefully makes #3695 easier. It also enables cni v0.3 and ipv6. @sstabellini

RFE: Generate api sub-package, with (almost) no external dependencies.

20

### What do you want to happen? When generating api types with `kubebuilder create api`, it generates the corresponding Go types in `./api/v1`. However, it is unergonomic for external projects...

2.0: Consider daemonization

13

## Background The exec-based API can be awkward for a few reasons: - Many plugins need a daemon anyways - Writing binaries to disk is a security risk - Executing...

2.0: Protobuf / gRPC: how to pass network configuration to plugins?

1

Assuming we move forward with daemonization (#821), then we will have to write a protobuf schema for the CNI protocol. This tpresents a few awkward edges around network configuration. The...

2.0: Device interactions

2

## The problem Right now, there isn't a standard way to allocate hardware devices outside of a CNI plugin. The flow, today, often looks like 1. User creates a Kubernetes...

Enhanced plugin / network lifecycle ( INIT / DEINIT / GC)

7

## Background CNI 1.0 has a very simple lifecycle: ADD and DELETE (and CHECK). This isn't perfect; there are some additional stages we may wish to capture. In general, these...