Migrating to Linkerd edge-25.3.3
Version edge-25.3.3 introduces 1 breaking change. This guide details how to update your code.
Released: 3/20/2025
1
Breaking Changes
2
Migration Steps
3
Affected Symbols
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
Link (CRD)proxy.cores (Helm value)proxy.runtime.workers (Helm value)Breaking Changes
●Issue #1
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
- 1If 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.
- 2If configuring proxy workers via Helm, replace the usage of `proxy.cores` with the new `proxy.runtime.workers` structure.
Release 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`.
Need More Details?
View the full release notes and all changes for Linkerd edge-25.3.3.
View Full Changelog