k3s-io/k3s v1.25.3+k3s1

on GitHub

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

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

Changes since v1.25.2+k3s1:

• E2E: Groundwork for PR runs (#6131)
• Fix flannel for deployments of nodes which do not belong to the same network and connect using their public IP (#6180)
• Mark v1.24.6+k3s1 as stable (#6193)
• Add cluster reset test (#6161)
• The embedded metrics-server version has been bumped to v0.6.1 (#6151)
• The ServiceLB (klipper-lb) service controller is now integrated into the K3s stub cloud controller manager. (#6181)
• Events recorded to the cluster by embedded controllers are now properly formatted in the service logs. (#6203)
• Fix error dialing backend errors in apiserver network proxy (#6216)
  • Fixed an issue with the apiserver network proxy that caused kubectl exec to occasionally fail with error dialing backend: EOF
  • Fixed an issue with the apiserver network proxy that caused kubectl exec and kubectl logs to fail when a custom kubelet port was used, and the custom port was blocked by firewall or security group rules.
• Fix the typo in the test (#6183)
• Use setup-go action to cache dependencies (#6220)
• Add journalctl logs to E2E tests (#6224)
• The embedded Traefik version has been bumped to v2.9.1 / chart 12.0.0 (#6223)
• Fix flakey etcd test (#6232)
• Replace deprecated ioutil package (#6230)
• Fix dualStack test (#6245)
• Add ServiceAccount for svclb pods (#6253)
• Update to v1.25.3-k3s1 (#6269)
• Return ProviderID in URI format (#6284)
• Corrected CCM RBAC to allow for removal of legacy service finalizer during upgrades. (#6306)
• Added a new --flannel-external-ip flag. (#6321)
  • When enabled, Flannel traffic will now use the nodes external IPs, instead of internal.
  • This is meant for use with distributed clusters that are not all on the same local network.

Embedded Component Versions

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