Releases: linkerd/linkerd2-proxy
Releases · linkerd/linkerd2-proxy
v2.175.0
This release alters the policy-related labels that the proxy sets on inbound traffic: * The `srv_kind` label is set with a value of "default" or "server", depending on whether the `srv_name` label correponds to a default policy or a `Server` resource. `srv_name` no longer includes a "default:" prefix for default policies. * The `saz_name` label is removed, replaced by `authz_kind` and `authz_name` labels. Similarly, the `authz_kind` label is either `default` or `serverauthorization`, and the `authz_name` label never includes a "default:" prefix.
v2.174.0
This release fixes an issue that could prevent proxies from sending HTTP Upgrade requests (e.g., for websockets) through multi-cluster gateways. Many dependencies have been updated, notably including a new version of `h2` that improves debug logging, avoids panics in time-related operations, and fixes an issue with parsing certain types of headers.
v2.173.0
This release updates the `tokio` and `tower` crates to unreleased versions to pickup workarounds for `Instant`-related panics that occur on Amazon Linux. This release also updates the proxy's configuration logic to stop logging errors when the inbound port configuration is empty.
v2.172.0
This release updates the proxy to avoid time substractions that are liable to panic.
v2.171.0
This release adds a new configuration variable, `LINKERD2_PROXY_ACCESS_LOG` that configures whether per-request access logs are emitted from inbound HTTP proxies. This variable may be set to `apache` for Apache Common Log output or `json` for JSON formatted logs. Access logs are emitted to stderr and the proxy's diagnostics logs are emitted to stdout.
v2.170.0
In addition to dependency updates, this change updates the inbound proxy to handle opaquely transported HTTP traffic. This fixes an issue encountered when a `Service`'s opaque ports annotation does not match that of the pods in the service. This situation should be rare.
v2.169.0
This release updates dependencies.
v2.168.0
This release includes no user-facing changes. The proxy's outbound HTTP router has been refactored to support upcoming changes.
v2.167.0
This release improves error logging when the proxy fails to accept a connection due to an operating system error.
v2.166.0
This release updates the proxy's `rustls`, `ring`, and `webpki` dependencies. Additionally, the proxy can now be built to use a `boringssl` backend instead of the default `rustls` backend, but this functionality is disabled in default builds.