k3s-io/k3s v1.18.10+k3s2

on GitHub

Warning: We’ve identified a critical bug in this release.

The bug can lead to objects being removed unexpectedly from K3s's database. When this occurs, these objects will no longer be available in the Kubernetes API. See k3s-io/kine#61 for more details.

We recommend that you do not use this release. If your cluster is already on this release, please upgrade to v1.18.12+k3s1.

This release provides improvements since the previous release of Kubernetes v1.18.10 in K3s v1.18.10+k3s1.

Major changes since v1.18.10+k3s1:

• Improve efficiency and reliability of Kine database compaction (#1311)
  When using SQLite or an external SQL datastore, this may cause a one-time delay in startup of the first node upgraded to this release. You can monitor creation of the new indexes by searching your logs for the messages Configuring database table schema and indexes, this may take a moment... and Database tables and indexes are up to date.
• install.sh (get.k3s.io) now automatically adds a Yum repo and installs the k3s-selinux package and dependencies on EL7/EL8-like systems (#2408)
  This can be disabled by exporting INSTALL_K3S_SKIP_SELINUX_RPM=true or INSTALL_K3S_SKIP_DOWNLOAD=true (the latter skips all downloads, including the K3s binary).

Embedded Component Versions

Versions for components not listed below have not changed since the previous release.

Known Issues

• As of this release, we are no longer providing RPMs as release artifacts. RPMs and the K3s Yum repo were not well-publicized offerings, and will require some refactoring to our CI pipeline before we can bring them back again.

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.