v1.34.10+k3s1
Changed 7
- Upgrade Kubernetes to v1.34.10
- Upgrade Traefik to v3.7.8
- Upgrade etcd to v3.6.14
- Upgrade mirrored-pause to 3.10.2
- Upgrade rancher/mirrored-coredns-coredns image version
- Upgrade rancher/mirrored-metrics-server image version
- Upgrade helm-controller and klipper-helm with --force-conflicts support
Fixed 2
- Fix typo in snapshot prune event
- Fix production builds always enabling Go coverage instrumentation
[!WARNING] This release upgrades Traefik chart to v40.x which includes a breaking change for the ingress-nginx migration: the provider name changes from
kubernetesIngressNginxtokubernetesIngressNGINX. Check https://github.com/traefik/traefik-helm-chart/releases/tag/v40.0.0 for more details
This release updates Kubernetes to v1.34.10, and fixes a number of issues.
For more details on what's new, see the Kubernetes release notes.
Changes since v1.34.9+k3s1:
- July Testing Backports (#14330)
- July K3s Build Rework + GHA bumps (#14335)
- Backports for 2026-07 (#14371)
- Bump mirrored-pause to 3.10.2 (#14391)
- Bump Traefik to v3.7.7 (#14379)
- More backports for 2026-07 (#14408)
- Fix typo in snapshot prune event (#14413)
- Bump rancher/mirrored-coredns-coredns image version (#14423)
- Bump golang:alpine image version (#14430)
- Bump rancher/mirrored-metrics-server image version (#14436)
- Use new Traefik v3.7.8 (#14427)
- Bump helm-controller and klipper-helm for
--force-conflictssupport (#14444) - Bump k3s-io/kubernetes and Go references (#14453)
- Bump etcd to v3.6.14 (#14463)
- Fix production builds always enabling Go coverage instrumentation (#14468)
- Bump helm-controller and klipper-helm (#14477)
Embedded Component Versions
| Component | Version |
|---|---|
| Kubernetes | v1.34.10 |
| Kine | v0.16.3 |
| SQLite | 3.53.2 |
| Etcd | v3.6.14-k3s1 |
| Containerd | v2.2.5-k3s2 |
| Runc | v1.4.2 |
| Flannel | v0.28.4 |
| Metrics-server | v0.9.0 |
| Traefik | v3.7.8 |
| CoreDNS | v1.14.6 |
| Helm-controller | v0.16.26 |
| Local-path-provisioner | v0.0.36 |
Helpful Links
As always, we welcome and appreciate feedback from our community of users. Please feel free to:
- Open issues here
- Join our Slack channel
- Check out our documentation for guidance on how to get started or to dive deep into K3s.
- Read how you can contribute here