chore(deps): update linkerd (major) #409
Open
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-linkerd
branch
4 times, most recently
from
61bf671 to
2956831
Compare
renovate
bot
force-pushed
the
renovate/major-linkerd
branch
4 times, most recently
from
dad4ed3 to
208fd7f
Compare
renovate
bot
force-pushed
the
renovate/major-linkerd
branch
2 times, most recently
from
5810959 to
e8cb6be
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-linkerd
branch
from
e8cb6be to
89649a5
Compare
renovate
bot
force-pushed
the
renovate/major-linkerd
branch
2 times, most recently
from
7096c5f to
83725bc
Compare
renovate
bot
force-pushed
the
renovate/major-linkerd
branch
from
83725bc to
6be5592
Compare
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:
1.17.0-edge->2025.1.21.8.0->2025.1.230.13.0-edge->2025.1.2edge-23.9.4->edge-25.1.2edge-23.9.3->edge-25.1.2Release Notes
linkerd/linkerd2 (linkerd/linkerd2)
vedge-25.1.2Compare Source
What's Changed
New Contributors
Full Changelog: linkerd/linkerd2@edge-25.1.1...edge-25.1.2
vedge-25.1.1Compare Source
Overall status: RECOMMENDED
Cautions
This release requires that the Kubernetes API server be able to use TLS v1.3. That's been supported since Kubernetes v1.19, and Linkerd currently requires at least Kubernetes v1.22, so this shouldn't be an issue for anyone. It also validates that
proxy.runAsRootbe set ifproxyInit.closeWaitTimeoutSecsis set -- this was a functional requirement anyway, but we now validate it at install time.Changes
Welcome to 2025! This first release of the year bumps the minimum TLS version when talking to the API server to v1.3 (see the CAUTIONS above), adds proper iptables support for RHEL nodes, allows Linkerd to talk to running Pods which haven't passed readiness checks yet (thanks, Tuomo!), and allows specifying both
podAnnotationsper deployment (thanks, Takumi Sue!) and labels for the Viz dashboard (thanks, omer2500!). It also validates thatproxy.runAsRootis set if you try to setproxyInit.closeWaitTimeoutSecs, correctly handles proxy log levels with quotes, cleans up CLI output of port forwarding errors, adds the pod UID and proxy container name to the environment, fixes a bug with installing extensions with Helm in IPv6 clusters, and removes some unneeded CNI configuration values. Finally, thanks to Joakim Roubert for cleaning up some development shell scripting!What's Changed
0.14.28to0.14.32by @cratelyn in https://github.com/linkerd/linkerd2/pull/13492New Contributors
Full Changelog: linkerd/linkerd2@edge-24.11.8...edge-25.1.1
vedge-24.11.8Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
This release bumps dependencies to change Linkerd's logic around Kubernetes leases to make sure that patches don't get stuck indefinitely.
What's Changed
Full Changelog: linkerd/linkerd2@edge-24.11.7...edge-24.11.8
vedge-24.11.7Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
This release removes the initial delay for the policy controller, allowing for faster control-plane startups, quietens the policy controller's reconciliation logs, and adds logging to make it clear which policy-controller pod is responsible for updating statuses.
What's Changed
Full Changelog: linkerd/linkerd2@edge-24.11.6...edge-24.11.7
vedge-24.11.6Compare Source
Overall status: NOT RECOMMENDED, use edge-24.11.7 instead
Cautions
edge-24.11.6 has been superseded by edge-24.11.7.
Changes
edge-24.11.6 has been superseded by edge-24.11.7.
What's Changed
Full Changelog: linkerd/linkerd2@edge-24.11.5...edge-24.11.6
vedge-24.11.5Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
In this release, the proxy emits new
request_frame_sizeandresponse_frame_sizemetrics with information about TCP frame distributions, correctly accounts for closed connections in route metrics, and fixes a (rare) panic for resources in whichmanagedFieldshas no timestamp. Additionally,linkerd checkchecks to be sure that your Link resources match your CLI version, keywords indocker buildnow use correct cases (thanks, Derek Brown!), and we now test Linkerd on Kubernetes 1.31.What's Changed
Full Changelog: linkerd/linkerd2@edge-24.11.4...edge-24.11.5
vedge-24.11.4Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
This release fixes a bug (issue 13327) where Linkerd could constantly re-update the
statusclause of HTTPRoute if another Gateway API controller was present in the system (thanks Derek Brown!), ensures that all of the proxy-injector's logs are valid JSON when JSON logging is enabled (thanks, Micah See!), and cleans up HTTPRoute validation to make sure that if abackendRefis a Service, it must have a valid port.What's Changed
New Contributors
Full Changelog: linkerd/linkerd2@edge-24.11.3...edge-24.11.4
vedge-24.11.3Compare Source
Overall status: RECOMMENDED
Cautions
N/A
Changes
edge-24.11.3 brings local rate limiting to Linkerd! Using the new HTTPLocalRateLimitPolicy resource, you can attach rate limits to Servers to protect workloads from being overwhelmed by excessive traffic. Additionally, it improves metrics for TCPRoute and TLSRoute egress control, correctly handles the case where a Route type changes parents (fixing [issue #13280]), allows
linkerd diagnostics endpointsto correctly handle workloads with multiple endpoints, and removes unneeded references tolinkerd-basefrom thelinkerd-control-planechart README (thanks, Brandon Ros!).What's Changed
shortnames: []from HTTPLocalRateLimitPolicy by @alpeb in https://github.com/linkerd/linkerd2/pull/13297Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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.