Releases: linkerd/linkerd2-proxy-init
Releases · linkerd/linkerd2-proxy-init
validator v0.1.4
Dependencies updates
cni-plugin v1.6.4
Dependencies updates
proxy-init v2.4.3
proxy-init/v2.4.3 * Dependencies updates
cni-plugin v1.6.3
cni-plugin/v1.6.3
- fix(cni-plugin): append inbound skip ports instead of replacing
- fix(cni-plugin): fix several race conditions
- Dependencies updates
validator v0.1.3
chore(build): bump validator crate version (#538) Signed-off-by: Zahari Dichev <[email protected]>
cni-plugin v1.6.2
Fixed shutdown issue This release fixes an issue introduced in v1.6.0 where the linkerd-cni pod was failing to complete its cleanup tasks during shutdown, leaving the linkerd-cni active but potentially with revoked permissions, thus interfering with the proper startup of pods in the node.
cni-plugin v1.6.1
Improved SA token rotation detection This release improves the service account token rotation detection introduced in the previous release.
proxy-init v2.4.2
proxy-init/v2.4.2 Dependencies updates
cni-plugin v1.6.0
SA token rotation detection, RHEL nodes support This release adds support for detecting whenever the service account token mounted as a projected volume into the linkerd-cni DaemonSet is rotated. Also, we add support for a new iptables mode "plain" that implies running the `iptables` command (instead of `iptables-legacy` or `iptables-nft`), useful for nodes running RHEL.
cni-plugin v1.5.2
Don't ignore inotifywait failures This release fixes the issue that when the node had hit the inotify limit, deploying the linkerd-cni daemonset would silently fail. Now the problem is caught and the pod enters a crash loop until the limit is no longer surpassed.