Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 15, 2025

Bumps the linkerd group with 1 update: github.com/linkerd/linkerd2.

Updates github.com/linkerd/linkerd2 from 0.5.1-0.20250723143138-3095b3fef660 to 18.9.1+incompatible

Release notes

Sourced from github.com/linkerd/linkerd2's releases.

stable-2.14.10

NOTE about 2.15 and beyond: As of February 2024, the Linkerd project is no longer producing open source stable release artifacts. Please read the 2.15 announcement for details.

See the full list of Linkerd releases for ways to get Linkerd.

stable-2.14.10

This stable release back-ports bugfixes and improvements from recent edge releases.

  • Introduced support for arbitrary labels in the podMonitors field in the control plane Helm chart (thanks @​jseiser!) (#11222; fixes #11175)
  • Added a prometheusUrl field for the heartbeat job in the control plane Helm chart (thanks @​david972!) (#11343; fixes #11342)
  • Updated the Destination controller to return INVALID_ARGUMENT status codes properly when a ServiceProfile is requested for a service that does not exist. (#11980)
  • Reduced the load on the Destination controller by only processing Server updates on workloads affected by the Server (#12017)
  • Changed how updates to a Server selector are handled in the destination service. When a Server that marks a port as opaque no longer selects a resource, the resource's opaqueness will reverted to default settings (#12031; fixes #11995)
  • Fixed a race condition in the destination service that could cause panics under very specific conditions (#12022; fixes #12010)
  • Fixed an issue where inbound policy could be incorrect after certain policy resources are deleted (#12088)

#11222: linkerd/linkerd2#11222 #11175: linkerd/linkerd2#11175 #11343: linkerd/linkerd2#11343 #11342: linkerd/linkerd2#11342 #11980: linkerd/linkerd2#11980 #12017: linkerd/linkerd2#12017 #11995: linkerd/linkerd2#11995 #12031: linkerd/linkerd2#12031 #12010: linkerd/linkerd2#12010 #12022: linkerd/linkerd2#12022 #12088: linkerd/linkerd2#12088

stable-2.14.9

This stable release adds a cni-repair-controller which fixes the issue of injected pods that cannot acquire proper network config because linkerd-cni and/or the cluster's network CNI haven't fully started (#11699). It also fixes a bug in the destination controller where having a large number of Server resources could cause the destination controller to use an excessive amount of CPU (#11907). Finally, it fixes a conflict with tap resource shortnames which was causing warnings from kubectl v1.29.0+ (#11816).

... (truncated)

Changelog

Sourced from github.com/linkerd/linkerd2's changelog.

Changes

Please visit Linkerd's Release page for for the latest release notes moving forward!

edge-24.2.5

  • Migrated edge release change notes to use GitHub's automated release notes feature.

edge-24.2.4

  • Updated the ExternalWorkload CRD to v1beta1, renaming the meshTls field to meshTLS (#12098)
  • Updated the proxy to address some logging and metrics inconsistencies (#12099)

#12098: linkerd/linkerd2#12098 #12099: linkerd/linkerd2#12099

edge-24.2.3

  • Allowed the MutatingWebhookConfig timeout value to be configured (#12028) (thanks @​mikebell90)
  • Added a counter for items dropped from destination controller workqueue (#12079)
  • Fixed a spurious linkerd check error when using container images with digests (#12059)
  • Fixed an issue where inbound policy could be incorrect after certain policy resources are deleted (#12088)

#12028: linkerd/linkerd2#12028 #12079: linkerd/linkerd2#12079 #12059: linkerd/linkerd2#12059 #12088: linkerd/linkerd2#12088

edge-24.2.2

This release addresses some issues in the destination service that could cause it to behave unexpectedly when processing updates.

  • Fixed a race condition in the destination service that could cause panics under very specific conditions (#12022; fixes #12010)
  • Changed how updates to a Server selector are handled in the destination service. When a Server that marks a port as opaque no longer selects a resource, the resource's opaqueness will reverted to default settings (#12031; fixes #11995)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot dependabot bot requested a review from davidcollom as a code owner December 15, 2025 08:24
@dependabot dependabot bot force-pushed the dependabot/go_modules/linkerd-03da459da0 branch from 004922a to 470ad14 Compare December 16, 2025 17:44
@davidcollom
Copy link
Owner

@dependabot recreate

Bumps the linkerd group with 1 update: [github.com/linkerd/linkerd2](https://github.com/linkerd/linkerd2).


Updates `github.com/linkerd/linkerd2` from 0.5.1-0.20250723143138-3095b3fef660 to 18.9.1+incompatible
- [Release notes](https://github.com/linkerd/linkerd2/releases)
- [Changelog](https://github.com/linkerd/linkerd2/blob/main/CHANGES.md)
- [Commits](https://github.com/linkerd/linkerd2/commits/v18.9.1)

---
updated-dependencies:
- dependency-name: github.com/linkerd/linkerd2
  dependency-version: 18.9.1+incompatible
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: linkerd
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/linkerd-03da459da0 branch from 470ad14 to 1aba34e Compare December 16, 2025 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant