Skip to content

v1.18.2+k3s1
Compare
Choose a tag to compare
@cjellick cjellick released this 07 May 00:17
· 62 commits to release-1.18 since this release
v1.18.2+k3s1
698e444
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This release is k3s's first in the v1.18 line. It upgrades Kubernetes to version v1.18.2, introduces several enhancements and many bug fixes, and addresses an upstream runc CVE.

Features and Enhancements

  • Kubernetes upgraded to v1.18.2
  • K3s now supports multiple release channels including "stable" and "latest" as well as minor-version specific channels like v1.18, v1.17, v1.16 See our documentation for more details.
  • Our experimental support for SELinux in K3s's embedded containerd continues to improve. We've addressed several bugs found by the community, which are list in the major bug fixes section. See the documentation for more details on SELinux.

Major bug fixes since v1.17.4+k3s1

  • Fixed an issue where helm charts managed by k3s's helm-controller could not successfully upgrade #1299
  • Fixed an issue causing excessive CPU usage in postgres database backends #1392
  • Fixed an issue where kubectl top would not work with docker as the CRI #1554
  • Fixed several issues related to k3s's experimental SELinux support #1583 #1630 #1666
  • Fixed an issue where helm charts managed by k3s's helm-controller would not work properly if they were outside the kube-system namespace #1602
  • Fixed an issue where a rolling upgrade of server nodes in an HA configuration would cause coreDNS and other services to flap #1607
  • Fixed an issue where k3s could crash due to thread exhaustion when talking to the database #1628
  • Fixed an issue where remounting a persistent volume after pod deletion could fail #1682
  • Fixed an issue with getting the proper version of k3s when installing via the install script #1751
  • Upgraded the runc shipped with our embedded containerd to address an upstream CVE #1743

Important

Note, that starting in release v1.17.4+k3s1, we've begun using mirrored versions of the traefik and coredns images.

  • The coredns/coredns image is now rancher/coredns-coredns
  • The library/traefik image is now rancher/library-traefik
    If you are upgrading to this version from a version prior to v1.17.4+k3s1, this will cause these services to be redeployed upon upgrade. If you are running k3s in an air-gapped environment, you must mirror these images to your private registry. Please refer to our air-gap documentation for details.

Helpful Links

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

Assets 14