What k3s-io/k3s shipped
Generated by FoxPlug from public activity — not affiliated with K3s.
Week of September 14, 2026
What shipped
- Kubernetes v1.37.0 is now available in K3s as v1.37.0+k3s1. Release
- KMS providers are now excluded from apiserver readiness checks, allowing kubelet to start before KMS providers are available. Pull request #14635
- K3s now waits up to 60 seconds for a default network route to appear during startup instead of failing immediately. Pull request #14527
- Release 1.37 branch received backports including network route detection and KMS provider fixes. Pull request #14631
- Release 1.36 branch received backports for etcd store fix and network improvements. Pull request #14632
- Release 1.35 branch received backports for etcd store fix and network improvements. Pull request #14633
- Release 1.34 branch received backports for etcd store fix and network improvements. Pull request #14634
Why it matters
K3s v1.37.0 ships with Kubernetes 1.37.0 and fixes startup reliability issues when network routes or KMS providers are not immediately available. These fixes are backported across multiple release branches to address real-world deployment scenarios.
Changelog entry
- Kubernetes updated to v1.37.0 Release
- KMS providers excluded from apiserver readiness check to allow kubelet startup before KMS providers are available Pull request #14635
- Added 60-second wait for default network route during host interface detection to prevent startup failures Pull request #14527
Post for X
[6] K3s v1.37.0+k3s1 is available, updating Kubernetes to v1.37.0 with fixes for network route detection and KMS provider startup handling.
Post for LinkedIn
[6] K3s v1.37.0+k3s1 is now available with Kubernetes v1.37.0. This release improves startup reliability with fixes for network route detection [1] and KMS provider initialization [0], ensuring K3s clusters can start reliably in varied network environments.