K3s v1.35.7+k3s1

v1.35.7+k3s1
Changed 7
  • Upgrade Kubernetes to v1.35.7
  • Upgrade Traefik to v3.7.8
  • Upgrade etcd to v3.6.14
  • Upgrade mirrored-pause to 3.10.2
  • Upgrade helm-controller and klipper-helm with support for --force-conflicts flag
  • Upgrade rancher/mirrored-coredns-coredns image
  • Upgrade rancher/mirrored-metrics-server image
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 kubernetesIngressNginx to kubernetesIngressNGINX. Check https://github.com/traefik/traefik-helm-chart/releases/tag/v40.0.0 for more details

This release updates Kubernetes to v1.35.7, and fixes a number of issues.

For more details on what's new, see the Kubernetes release notes.

Changes since v1.35.6+k3s1:
  • July Testing Backports (#14329)
  • July K3s Build Rework + GHA bumps (#14333)
  • Backports for 2026-07 (#14370)
  • Bump mirrored-pause to 3.10.2 (#14390)
  • Bump Traefik to v3.7.7 (#14380)
  • More backports for 2026-07 (#14407)
  • Fix typo in snapshot prune event (#14412)
  • Bump rancher/mirrored-coredns-coredns image version (#14421)
  • Bump golang:alpine image version (#14431)
  • Bump rancher/mirrored-metrics-server image version (#14439)
  • Use new Traefik v3.7.8 (#14425)
  • Bump helm-controller and klipper-helm for --force-conflicts support (#14443)
  • Bump k3s-io/kubernetes and Go references (#14455)
  • Bump etcd to v3.6.14 (#14462)
  • Fix production builds always enabling Go coverage instrumentation (#14467)
  • Bump helm-controller and klipper-helm (#14476)
Embedded Component Versions
ComponentVersion
Kubernetesv1.35.7
Kinev0.16.3
SQLite3.53.2
Etcdv3.6.14-k3s1
Containerdv2.2.5-k3s2
Runcv1.4.2
Flannelv0.28.4
Metrics-serverv0.9.0
Traefikv3.7.8
CoreDNSv1.14.6
Helm-controllerv0.17.7
Local-path-provisionerv0.0.36
Helpful Links

As always, we welcome and appreciate feedback from our community of users. Please feel free to:

View original

Upgraded? How did it go?

Discussion