v2.182.0

This release updates the proxy's service discovery module to avoid
redundant load balancer updates that could cause unnecessary connection
churn.

This release also includes improvements to the proxy's retry handling of
gRPC requests. The proxy would not retry requests when a response's
status code was emitted in a TRAILERS frame. This has been fixed.

This release also includes a number of internal changes that set up for
per-route authorization. There should be no user-facing impact at this
point except for the introduction of additional metrics labels.

This release cherry-picks commits from the `main` branch into the

`release/v2.161` branch, including fixes for a panic when processing a
large number of service discovery updates, for incorrect handling of
`CONNECT` requests with `Content-Length` headers, and for a failure to
correctly resolve DNS SRV records for the control plane.

v2.181.0

This release fixes a bug in the proxy's outbound load balancer that
could cause panics, especially when the balancer processes many service
discovery updates in a short period of time.

v2.180.0

This release includes only minor internal changes and dependency
updates.

v2.179.0

This release fixes a problem with HTTP/1.1 `CONNECT` requests. When a
server responds to a `CONNECT` request with `content-length` or
`transfer-encoding` headers (in violation of RFC 7231), the proxy must
actively strip these headers to avoid making the Hyper server fail the
response.

v2.178.0

This release fixes an issue with the way proxies discover control plane
components via DNS. When `SRV` records cannot be resolved, the proxy
would no not necessarily fall back to resolving `A` records. This has
been fixed.

The inbound proxy can now discover policies dynamically. Ports that are
configured in the `LINKERD2_PROXY_INBOUND_PORTS` are discovered as the
proxy starts up; but now the proxy will discover policies for ports that
are not in this list. The pod's default policy is used initially, but
once a policy is received from the control plane it is used.

v2.177.0

This release updates "ingress-mode" proxies to be able to forward
non-HTTP traffic within the cluster. Protocol detection is always
attempted for outbound connections, however, when in ingress mode.

This release also adds a new `process_uptime_seconds_total` metric.

v2.176.0

This release fixes an issue where proxies would not honor the cluster's
opaqueness settings for non-pod/service addresses. This could cause
protocol detection to be peformed, for instance, when using off-cluster
databases.

This release also disables the use of regexes in Linkerd log filters
(i.e., as set by `LINKERD2_PROXY_LOG`). Malformed log directices could,
in theory, cause a proxy to stop responding.

v2.161.3

This release fixes opaqueness settings when communicating with
non-pod/service addresses.

v2.161.2

This release cherry-picks commits from the main branch into the
release/v2.161 branch, including fixes for multicluster gateways. This
change does NOT include changes to the proxy's TLS infrastructure, as
these changes are not backwards-compatible.