k3s-io/k3s v1.19.5+k3s2

on GitHub

This release reverts the packaged CoreDNS version from v1.7.1 to 1.6.9 to fix an issue with intermittent DNS resolution failure when looking up records from DNSSEC-enabled domains. (coredns/coredns#4189 / k3s-io/k3s#2700)

Changes since v1.19.5+k3s1:

• Revert CoreDNS version from 1.7.1 to 1.6.9

Known Issues

• 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.
• There is a regression that may cause issues with deleting nodes due to finalizers not being removed. If you observe a node is stuck for some time and is not being deleted you can describe the node to see if any finalizers remain. If there are any finalizers, you can work around this issue by running the following command to remove the finalizers:

# replace <nodename> with the name of the node
kubectl get node -o name <nodename> | xargs -i kubectl patch {} -p '{"metadata":{"finalizers":[]}}' --type=merge

Notice

As of v1.19.4+k3s2, the testing channel (available as one of the K3s release channels) ONLY serves pre-releases such as RCs, alphas, and betas. Previously, it served both pre-releases and fully graduated ones.

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.