v2.113.2-test

Fixes outbound caching

v2.113.1-test

Testing https://github.com/linkerd/linkerd2-proxy/pull/697
and https://github.com/linkerd/linkerd2-proxy/pull/698

v2.113.0

This release includes changes to TCP metrics to ensure that peer
identities are encoded via the `client_id` and `server_id` labels.

v2.112.0

This release fixes a bug introduced in v2.111.0 that could cause
outbound connections to idle out during TLS handshakes.

v2.111.0

This release increases the default timeout for DNS resolution to 500ms,
as there were reports that 100ms was too restrictive.

This also includes several internal changes to facilitate
connection-oriented caching; but these changes are not expected to
impact runtime behavior.

v2.110.0

This release fixes a recent regression in multicluster gateway
configurations that would forbid inbound gateway traffic. It also fixes
URI normalization for orig-proto-upgrade requests that do not include a
`Host` header.

v2.109.0

This release includes several major changes to the proxy's behavior:

- Service profile lookups are now necessary and fundamental to outbound
  discovery for HTTP traffic. That is, if a service profile lookup is
  rejected, endpoint discovery will not be performed; and endpoint
  discovery must succeed for all destinations that are permitted by
  service profiles. This simplifies caching and buffering to reduce
  latency (especially under concurrency).
- Service discovery is now performed for all TCP traffic, and
  connections are balanced over endpoints according to connection
  latency.
- This enables mTLS for **all** meshed connections; not just HTTP.
- Outbound TCP metrics are now hydrated with endpoint-specific labels.

v2.108.0

This release improves error handling for DNS errors encountered when
discovering control plane addresses. Such errors are common during
installation, before all components have been started.

v2.107.0

This release includes internal changes to the service discovery system,
espcially when discovering control plane components (like the
destination and identity controllers). Now, the proxy attempts balance
requests across all pods in each control plane service. This requires
control plane changes to use "headless" services so that SRV records are
exposed. When the control plane services have a `clusterIP` set, the
proxy falls back to using normal A-record lookups.

v2.106.0

This release enables a multi-threaded runtime. Previously, the proxy
would only ever use a single thread for data plane processing; now, when
the proxy is allocated more than 1 CPU share, the proxy allocates a
thread per available CPU. This has shown substantial latency
improvements in benchmarks, especially when the proxy is serving
requests for many concurrent connections.