Skip to content

v1.19.3+k3s3
Compare
Choose a tag to compare
@davidnuzik davidnuzik released this 13 Nov 07:14
· 112 commits to release-1.19 since this release
v1.19.3+k3s3
0e4fbfe

This release addresses a critical bug present in the following releases:

  • v1.19.3+k3s2
  • v1.18.10+k3s2
  • v1.17.14+k3s1
  • v1.17.13+k3s2

This release is for the v1.19.x release train. Releases addressing this bug are also available for the 1.17.x and 1.18.x release trains. If you are on any of the affected versions, it is recommended that you upgrade.

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.

Known Issues

The following known issues are carried forward from our previous release, v1.19.3+k3s2. These are not new to this release.

  • As of v1.19.3+k3s2, we no longer provide 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.
  • When using managed etcd, nodes that are deleted from the cluster, or fail partway through joining the cluster, cannot be automatically rejoined without manual intervention. You may see one of the following errors in the logs on the joining node: 
    node has been delete from the cluster. Backup and delete ${datadir}/server/db if you like to rejoin the node
etcd stopped - if this node was removed from the cluster, you must backup and delete /var/lib/rancher/k3s/server/db/etcd before rejoining
    If you see these messages, follow the instructions to clean up the node's copy of the etcd database before rejoining the node. This will be handled automatically in a future release.
  • We've been working through issues in our experimental SELinux support in order to promote it to stable. We expect to promote it in a future v1.19 release. Upgrades of systems that have the experimental SELinux support turned on will not function correctly unless additional steps are taken:
    • Enablement of SELinux in embedded containerd is no longer automatic. Prior to the v1.19 release line, K3s would auto-detect whether SELinux MCS label support should be enabled. You must now explicitly turn it on by supplying the --selinux flag. Because of this change, the --disable-selinux flag has been deprecated (and it is an error to specify both). See the docs for details.

Embedded Component Versions

Component Version
Kubernetes v1.19.3
SQLite 3.33.0
Etcd v3.4.13-k3s1
Containerd v1.4.1-k3s1
Flannel v0.12.0-k3s1
Metrics-server v0.3.6
Traefik 1.7.19
CoreDNS v1.6.9
Helm-controller v0.7.3
Local-path-provisioner v0.0.14

Helpful Links

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

Assets 14
Loading