Shipped · DevOps and infrastructure

What linkerd/linkerd2 shipped

The public repository of Linkerd · github.com/linkerd/linkerd2

Written by FoxPlug from the repository's own releases; not affiliated with Linkerd. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/linkerd/linkerd2; Linkerd did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for linkerd2, free

Week of November 2, 2026

What shipped

Why it matters

This week brings a new edge release plus a fix for namespace-level native sidecar annotations that had stopped taking effect. Build and CI work also removes leftover proxy build files and makes integration jobs less likely to fail on external lookups or control plane timing.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Edge-26.11.1 is out. Also this week: the deprecated namespace annotation for disabling native sidecars works again, proxy builds no longer leave untracked files in the repo root, k3s images are pinned to stop update.k3s.io lookups breaking integration jobs, and the k8s testing re

Post for LinkedIn

This week's Linkerd updates: edge-26.11.1 is released, with golang.org/x/net bumped to 0.62.0, the dev image moved to v53 and network-validator upgraded to 0.1.10. Injection now again honors config.beta.linkerd.io/proxy-enable-native-sidecar: "false" on a namespace, so new pods there no longer get a native sidecar when native sidecars are the default. Proxy builds write their apko tarball and SBOMs into a dedicated location instead of leaving untracked files in the repo root. On CI, policy tests now wait for the control plane deployment and pods, k3s images are pinned to avoid update.k3s.io lookups, and the Kubernetes testing ref is bumped to 1.37. The dev image is now v55, back on Debian bookworm.

Week of October 26, 2026

What shipped

Why it matters

This week's edge release carries a policy-controller fix for gRPC connection resets and a TLS fix for the tap API server, so users on the edge channel get more stable policy and tap behavior. The proxy moved to v2.372.0 and the dev and test toolchain was refreshed through the dev image, Go and Rust updates.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Edge-26.10.2 is out: policy-controller raises its gRPC h2 connection window to avoid GOAWAYs, the client now provides TLS for the tap API server, plus proxy v2.371.0. Proxy also moved to v2.372.0, and dev, Go and Rust dependencies were refreshed.

Post for LinkedIn

Edge-26.10.2 is out. The policy-controller now raises its gRPC h2 connection window to avoid GOAWAYs, which should cut down on connection resets. The client now provides TLS for the tap API server, contribution guidelines were updated, and the release bundles proxy v2.371.0. Separately the proxy moved to v2.372.0. On the maintenance side, the dev image is now v53, Rust dependencies were updated, and the Go version update patches the CA issue for the Go test images.

Week of October 19, 2026

What shipped

Why it matters

This week brought four edge releases with fixes for a destination controller panic and a stale policy-controller lease watch, plus a build update to golang 1.26.9 that closes five known vulnerabilities. Users tracking the recommended edge channel get these corrections, and the toolchain bump reduces exposure to those CVEs.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Four edge releases this week: edge-26.8.4 fixes a potential destination controller panic when deleting ExternalWorkloads and picks the TLSRoute API version from the cluster; edge-26.8.3 logs the requested path in structured access logs; edge-26.8.2 drops a duplicate Job informer;

Post for LinkedIn

This week brought four recommended edge releases. edge-26.8.4 corrects a potential panic in the destination controller when deleting ExternalWorkloads and determines the TLSRoute API version by examining the cluster. edge-26.8.3 includes the requested path when structured access logs are enabled, and bumps oras-go to 2.6.2 and the proxy to v2.366.0. edge-26.8.2 removes a duplicate Job informer to avoid a pointless Prometheus error and exits the policy-controller if its lease watch dies so Kubernetes can restart it. edge-26.8.1 reenables the gosec G402 minimum TLS version rule now that golangci-lint handles it correctly. Separately, the build moved to golang 1.26.9, addressing five Go vulnerabilities.

More from linkerd/linkerd2 on GitHub

Merged pull requests

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.