●Change8

edge-25.3.3

Breaking Changes
📦 linkerd
⚠ 1 breaking✨ 4 features🐛 3 fixes🔧 3 symbols

Summary

This edge release integrates service-mirroring controllers into the multicluster extension for better GitOps management and updates federated Service metadata synchronization logic. It also replaces the `proxy.cores` Helm value with `proxy.runtime.workers`.

⚠️ Breaking Changes

  • The `proxy.cores` Helm chart value has been removed and replaced by the more flexible `proxy.runtime.workers` structure. Users must update their Helm configuration to use `proxy.runtime.workers` instead of `proxy.cores`.

Migration Steps

  1. If using federated Services, upgrade your Link resources by following the instructions in the [upgrading multicluster](/2.18/tasks/upgrading-multicluster/) documentation to utilize the new metadata synchronization behavior.
  2. If configuring proxy workers via Helm, replace the usage of `proxy.cores` with the new `proxy.runtime.workers` structure.

✨ New Features

  • Service-mirroring controllers are now integrated into the Linkerd multicluster extension for better GitOps management of Link `v1alpha3` CRs and credential Secrets.
  • When using federated Services, the metadata of the federated Service will now be kept in sync with the member Service that has the oldest Link.
  • It is now possible to set an environment variable to reenable outbound hostname metrics.
  • Custom debug container annotations are now correctly honored during injection.

🐛 Bug Fixes

  • The multicluster mirror controller unintentionally switched to use ClusterRole permissions instead of Role permissions (this was present in this release but fixed in recommended alternatives).
  • Corrected Helm manifest whitespacing.
  • The injector now uses annotated values for the debug container.

🔧 Affected Symbols

Link (CRD)proxy.cores (Helm value)proxy.runtime.workers (Helm value)