●Change8

edge-25.4.1

📦 linkerd
✨ 7 features🐛 2 fixes⚡ 1 deprecations🔧 3 symbols

Summary

This release fixes issues related to Gateway API CRD installation and updates Prometheus configuration for new multicluster controllers. It also introduces support for restoring inbound authority labels via an environment variable.

Migration Steps

  1. If you are using the new GitOps-compatible multicluster functionality (introduced in edge-25.3.3), you must upgrade your Link resources by following the instructions at /2.18/tasks/upgrading-multicluster/.
  2. If you are installing Linkerd, ensure Gateway API CRDs are installed beforehand, or explicitly set `installGatewayAPI=true` when using the Linkerd CLI, as Gateway API CRDs are now required starting with edge-25.3.4.

✨ New Features

  • Linkerd CLI now correctly supports setting `installGatewayAPI=true` during installation.
  • Added `--only-controller` flag to the deprecated `linkerd mc unlink` command to aid migration by removing old mirror controllers while preserving Link resources.
  • Proxy now supports restoring `authority` labels on inbound metrics via the `LINKERD2_PROXY_INBOUND_AUTHORITY_LABELS=unsafe` environment variable.
  • Introduced a new metric: `control_dns_resolutions_total`.
  • Span context is now correctly propagated into proxy debug log messages for easier debugging.
  • Prometheus configuration is updated to correctly scrape the new multicluster mirror controllers.
  • Policy tests now run against various Gateway API versions in CI.

🐛 Bug Fixes

  • Fixed an issue where Linkerd would error during CRD installation if `installGatewayAPI` was not explicitly checked.
  • Correctly configured Prometheus to scrape the new multicluster mirror controllers (mentioned in Cautions and Changes sections).

🔧 Affected Symbols

linkerd mc unlinkLINKERD2_PROXY_INBOUND_AUTHORITY_LABELScontrol_dns_resolutions_total

⚡ Deprecations

  • The `linkerd mc unlink` command is deprecated; use the new multicluster controller migration path.