chore(deps): update linkerd - #1217
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/linkerd
branch
4 times, most recently
from
June 16, 2026 05:51
b20a215 to
ace4bfa
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/linkerd
branch
from
June 16, 2026 06:19
ace4bfa to
7fc0275
Compare
mikutas
force-pushed
the
main
branch
5 times, most recently
from
June 17, 2026 08:06
7705651 to
ccc11fa
Compare
renovate
Bot
force-pushed
the
renovate/linkerd
branch
2 times, most recently
from
June 22, 2026 03:22
cb860f6 to
9a9d624
Compare
renovate
Bot
force-pushed
the
renovate/linkerd
branch
from
July 11, 2026 02:53
9a9d624 to
cdd381e
Compare
renovate
Bot
force-pushed
the
renovate/linkerd
branch
from
July 20, 2026 20:58
cdd381e to
69dc3a2
Compare
renovate
Bot
force-pushed
the
renovate/linkerd
branch
from
July 30, 2026 18:16
69dc3a2 to
6889c13
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2025.8.1→2025.12.32025.8.1→2025.12.32025.8.1→2025.12.3edge-25.8.1→edge-25.12.3Release Notes
linkerd/linkerd2 (linkerd/linkerd2)
vedge-25.12.3Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
This release correctly discovers ports and port opacity when using native sidecars, and fixes a race condition in the CNI plugin that could prevent proper deployment in some environments, particularly EKS.
What's Changed
abdd2f6toe002140by @dependabot[bot] in #14799Full Changelog: linkerd/linkerd2@edge-25.12.2...edge-25.12.3
vedge-25.12.2Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
This release correctly takes
hostPorts and opaque ports into account when using native sidecars, and improves native sidecar support in thelinkerd authzandlinkerd check --proxycommands.What's Changed
linkerd authzby @alpeb in #14780linkerd check --proxyby @alpeb in #14779Full Changelog: linkerd/linkerd2@edge-25.12.1...edge-25.12.2
vedge-25.12.1Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
This release bumps dependencies but has no functional changes from
edge-25.11.3.What's Changed
2d752abtoabdd2f6by @dependabot[bot] in #14771New Contributors
Full Changelog: linkerd/linkerd2@edge-25.11.3...edge-25.12.1
vedge-25.11.3Compare Source
Overall status: RECOMMENDED
Cautions
As of this release, the
proxy-initimage has been merged into theproxyimage, which simplifies image management and reduces overall image size. Users who were explicitly using theproxy-initimage should use theproxyimage in its place.Changes
This release correctly honors the
timeouts.requestvalue of HTTPRoutes in thegateway.networking.k8s.ioAPI group, to match the behavior ofpolicy.linkerd.ioHTTPRoutes.What's Changed
Full Changelog: linkerd/linkerd2@edge-25.11.2...edge-25.11.3
vedge-25.11.2Compare Source
Overall status: NOT RECOMMENDED, use edge-25.11.3 instead
Cautions
In this release, mesh expansion does not correctly get certificates from SPIRE; we recommend using edge-25.11.3 instead.
Changes
This release fixes broken documentation URLs in CLI commands (thanks, beza!) and corrects a typo in the EgressNetwork and ExternalWorkload CRD definitions (thanks, YY!).
What's Changed
linkerd2-proxy-apiandtonicgroup by @sfleen in #14699bin/docker-buildfunctionality by @cratelyn in #146987006987to2d752abby @dependabot[bot] in #14740New Contributors
Full Changelog: linkerd/linkerd2@edge-25.11.1...edge-25.11.2
vedge-25.11.1Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
This release correctly includes pod metadata in OpenTelemetry traces, fixes the
workload_subscribersmetric to correctly track the total number of subscribers across all IP and port combinations (rather than only the most recent combination), and prevents a task leak when using federated services.What's Changed
dbf178cto7006987by @dependabot[bot] in #14686Full Changelog: linkerd/linkerd2@edge-25.10.7...edge-25.11.1
vedge-25.10.7Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
This release continues making Linkerd's Helm chart handle tracing parameters more robustly.
What's Changed
d03a93ctodbf178cby @dependabot[bot] in #14662Full Changelog: linkerd/linkerd2@edge-25.10.6...edge-25.10.7
vedge-25.10.6Compare Source
Overall status: NOT RECOMMENDED, use edge-25.10.7 instead
Cautions
N/A
Changes
This release continues making Linkerd's Helm chart handle tracing parameters more robustly.
What's Changed
Full Changelog: linkerd/linkerd2@edge-25.10.5...edge-25.10.6
vedge-25.10.5Compare Source
Overall status: NOT RECOMMENDED, use edge-25.10.7 instead
Cautions
N/A
Changes
This release makes Linkerd's Helm chart handle tracing parameters more robustly.
What's Changed
Full Changelog: linkerd/linkerd2@edge-25.10.4...edge-25.10.5
vedge-25.10.4Compare Source
Overall status: NOT RECOMMENDED, use edge-25.10.7 instead
Cautions
N/A
Changes
This release prevents a possible crash when injecting proxies without tracing configured, and includes semantic convention labels
user-agent.original,http.request.header.content-length,http.request.header.content-type, andhttp.request.header.l5d-orig-prototo OpenTelemetry spans.What's Changed
Full Changelog: linkerd/linkerd2@edge-25.10.3...edge-25.10.4
vedge-25.10.3Compare Source
Overall status: NOT RECOMMENDED, use edge-25.10.7 instead
Cautions
This release includes one breaking change: it removes the
ip_port_subscribersmetric and replaces it with the lower-cardinalityworkload_subscribersmetric.Changes
This release removes the
linkerd.io/proxy-root-parentandlinkerd.io/proxy-root-parent-kindlabels added to injected pods in edge-25.10.2. It also fixes a potential deadlock that could result in leaked tasks and unneeded memory consumption, and allows configuring the destination controller's stream queue capacity. The default remains 100 for the moment; lower values may be better for improving responsiveness to readiness and liveness issues.What's Changed
Full Changelog: linkerd/linkerd2@edge-25.10.2...edge-25.10.3
vedge-25.10.2Compare Source
Overall status: NOT RECOMMENDED, use edge-25.10.7 instead
Cautions
This release drops support for the (long-deprecated) OpenCensus trace protocol. Additionally, it adds the
linkerd.io/proxy-root-parentandlinkerd.io/proxy-root-parent-kindlabels to injected pods, but this change was reverted in edge-25.10.3 due to unforeseen issues.Changes
This release adds support for setting OpenTelemetry tracing values via
resource.opentelemetry.io/<label>annotations on pods, making it simpler to customize tracing for specific workloads. Additionally, it moves native sidecar support to beta, adding theconfig.beta.linkerd.io/proxy-enable-native-sidecarannotation and deprecating the alpha annotation (although that will continue to function).What's Changed
212f9a7tod03a93cby @dependabot[bot] in #14583Full Changelog: linkerd/linkerd2@edge-25.10.1...edge-25.10.2
vedge-25.10.1Compare Source
Overall status: RECOMMENDED
Cautions
This release drops support for the Linkerd Jaeger extension: instead, it supports directly configuring OpenTelemetry tracing by setting
controller.tracing.enableandcontroller.tracing.collector.endpointwhen installing Linkerd.Changes
This release guarantees that OpenTelemetry spans are flushed regularly, and not just when streams become idle. It also adds the
inbound_http_request_frame_size_bytesandinbound_grpc_request_frame_size_byteshistograms to metrics, to allow better visibility into request body sizes.What's Changed
4563c72to28cf3adby @dependabot[bot] in #14546linkerd-jaegerextension by @sfleen in #1455828cf3adto212f9a7by @dependabot[bot] in #14555Full Changelog: linkerd/linkerd2@edge-25.9.4...edge-25.10.1
vedge-25.9.4Compare Source
Overall status: RECOMMENDED
Cautions
Starting in this release, the
linkerd-crdsHelm chart will no longer install the Gateway API CRDs by default. To force the chart to install the Gateway API CRDs, setinstallGatewayAPI=truewhen installing the chart.If you previously used the
linkerd-crdschart to install the Gateway API CRDs, and you're running Linkerd 2.18/edge-25.4.4 or higher, upgrading with Helm will not uninstall the Gateway API CRDs. If you're upgrading from an earlier version, you will need to install the Gateway API CRDs manually.Changes
This release fixes an issue where native sidecar proxies could have stale endpoint data, resulting in problems routing traffic. Additionally, it correctly supports ReplacePrefixMatch in HTTPRoute RequestRedirect filters.
What's Changed
Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.