Releases: linkerd/linkerd2-proxy
Releases · linkerd/linkerd2-proxy
v2.105.0
This proxy release comprises mostly internal changes that set up for upcoming discovery changes. A `proxy_build_info` metric has been added to expose proxy build metadata via the admin interface, i.e., for Prometheus.
v2.104.1
This release only changes how release artifacts are named. There are no functional changes.
v2.104.0
This release primarily includes a fix for a regression in the tracing system introduced in v2.101.0. We have also made some internal changes to reduce latency in benchmarks.
v2.103.0
This release increases the default buffer size to match the proxy's in-flight request limit. This reduces contention in overload--especially high-concurrency--situations, substantially reducing tail latency.
v2.102.0
This release fixes a regression that could cause service profile lookups to be retried indefinitely, despite the server returning an `InvalidArgument` response (which indicates the proxy should not retry).
v2.101.0
This release primarily features an upgrade of the proxy's underlying Tokio runtime and its related libraries. We've observed lower latencies in initial benchmarks, but further testing and burn-in is warranted. Also, the proxy now honors the `LINKERD_PROXY_LOG_FORMAT=json` configuration to enable JSON-formatted logging.
v2.100.0
This change modifies the inbound gateway caching so that requests may be routed to multiple leaves of a traffic split.
v2.99.0
The proxy can now operate as gateway, routing requests from its inbound proxy to the outbound proxy, without passing the requests to a local application. This supports Linkerd's multicluster feature by adding a `Forwarded` header to propagate the original client identity and assist in loop detection.
v2.98.0
In some ingress setups, the proxy could be tricked into looping requests through the outbound proxy. We now detect these loops and fail these requests with a 502, saving your precious CPU.
v2.97.0
This release adds special handling for I/O errors in HTTP responses so that an `errno` label is included to describe the underlying errors in the proxy's metrics.