Skip to content

Releases: linkerd/linkerd2-proxy-init

cni-plugin v1.2.2

20 Sep 13:22
1ba375b
Compare
Choose a tag to compare

Dependency bumps and updated go to v1.21

proxy-init v2.2.2

07 Sep 13:00
defcee8
Compare
Choose a tag to compare
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

07 Sep 13:01
defcee8
Compare
Choose a tag to compare
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

01 Jun 14:55
982b933
Compare
Choose a tag to compare
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

04 May 23:07
cni-plugin/v1.1.3
15512bc
Compare
Choose a tag to compare
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

02 May 18:17
cni-plugin/v1.1.2
9f2f586
Compare
Choose a tag to compare
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

cni-plugin v1.1.1

18 Apr 23:35
9215ddf
Compare
Choose a tag to compare
Fixed incompatibility issue with AWS CNI addon in EKS, that was
forbidding pods to acquire networking after scaling up nodes.

validator v0.1.2

04 Apr 11:25
a18218e
Compare
Choose a tag to compare
* Dep bumps

proxy-init v2.2.1

03 Apr 18:23
90f6515
Compare
Choose a tag to compare
* Sanitize `subnets-to-ignore` flag
* Dependency bumps

cni-plugin v1.1.0

03 Apr 18:46
90f6515
Compare
Choose a tag to compare
* Add support for the `config.linkerd.io/skip-subnets` annotation
* Dependency bumps