cni-plugin v1.4.0

Add IPv6/dual-stack support

This release adds the linkerd-cni flag `--iptables-mode` (with possible values `legacy` and `nft`) and the `--ipv6` flag (default `true`).

After the set of rules run via iptables are processed, if `--ipv6` is true (which is the default), the same set of rules will be run via ip6tables.

proxy-init v2.2.4

Dependencies update

Upgraded Alpine to 3.19.0, and other various dependencies bumps.

cni-plugin v1.3.0

This release adds a linkerd-cni-repair-controller binary to the cni-plugin image. This controller watches over events on pods in the current node, which have been injected but are in a terminated state and whose linkerd-network-validator container exited with code 95. This means networking couldn't be properly set, probably because of a race between the linkerd CNI plugin and the main CNI plugin in the cluster. The controller then proceeds to delete those pods so they can restart with a proper network config.

proxy-init v2.2.3

Dependency bumps and updated go to v1.21

cni-plugin v1.2.2

Dependency bumps and updated go to v1.21

proxy-init v2.2.2

Address CVE-2023-2603

This release patches a security vulnerability, CVE-2023-2603. The
vulnerability is manifested in libcap v2.66. To address the CVE, the
alpine image (runtime) has been bumped; this in turn bumps libcap to
v2.69.

cni-plugin v1.2.1

Address CVE-2023-2603

This release patches a security vulnerability, CVE-2023-2603. The
vulnerability is manifested in libcap v2.66. To address the CVE, the
alpine image (runtime) has been bumped; this in turn bumps libcap to
v2.69.

cni-plugin v1.2.0

Drop "interface" mode

This release stops using the "interface" mode, and instead wait till
another CNI plugin drops a proper network config and then append the
linkerd CNI config to it. This avoids having pods start before proper
networking is established in the node.

cni-plugin v1.1.3

This release changes the CNI docker image to use `alpine:3.17.3` as the

base image, rather than `scratch`. This fixes a regression introduced
in v1.1.2, where the CNI init script could not actually run as
`scratch` images don't include a `bash` executable, while still
achieving the goal of minimizing the dependencies pulled by the
init docker image.

* cni: change base runtime image from `scratch` to `alpine`

cni-plugin v1.1.2

This release changes the CNI docker image to use `scratch` as the base image,
rather than `debian:bullseye-slim`. This reduces the size and runtime
dependencies of the CNI init container.

* cni: use `scratch` as the base runtime docker image