k3s-io/k3s v1.28.8+k3s1

on GitHub

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

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

Changes since v1.28.7+k3s1:

• Add an integration test for flannel-backend=none (#9608)
• Install and Unit test backports (#9641)
• Update klipper-lb image version (#9605)
• Chore(deps): Remediating CVE-2023-45142 CVE-2023-48795 (#9647)
• Adjust first node-ip based on configured clusterCIDR (#9631)
• Improve tailscale e2e test (#9653)
• Backports for 2024-03 release cycle (#9669)
  • Fix: use correct wasm shims names
  • The embedded flannel cni-plugin binary is now built and versioned separate from the rest of the cni plugins and the embedded flannel controller.
  • Bump spegel to v0.0.18-k3s3
  • Adds wildcard registry support
  • Fixes issue with excessive CPU utilization while waiting for containerd to start
  • Add env var to allow spegel mirroring of latest tag
  • Tweak netpol node wait logs
  • Fix coredns NodeHosts on dual-stack clusters
  • Bump helm-controller/klipper-helm versions
  • Fix snapshot prune
  • Fix issue with etcd node name missing hostname
  • Rootless mode should also bind service nodePort to host for LoadBalancer type, matching UX of rootful mode.
  • To enable raw output for the check-config subcommand, you may now set NO_COLOR=1
  • Fix additional corner cases in registries handling
  • Bump metrics-server to v0.7.0
  • K3s will now warn and suppress duplicate entries in the mirror endpoint list for a registry. Containerd does not support listing the same endpoint multiple times as a mirror for a single upstream registry.
• Docker and E2E Test Backports (#9707)
• Fix wildcard entry upstream fallback (#9733)
• Update to v1.28.8-k3s1 and Go 1.21.8 (#9746)

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