Skip to content

Release v0.6.0
Compare
Choose a tag to compare
@erikwilson erikwilson released this 19 Jun 00:49
v0.6.0
09b0634
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.

Release v0.6.0

K3s v0.6.0 provides important bug fixes and enhancements from our community and developers. This release brings external database and node label/taint functionality, as configuration and usability improvements remain the focus of k3s. Thanks to everyone in the community for the continued support and contributions!

Features and Enhancements

  • Default k3s.yaml to readable only by the user [#389] - Changes default k3s.yaml permissions from 0644 to 0600.
  • Add a check that the server time is set for SSL verification [#411] - Produce an error message unless the date is after 01/01/1980.
  • Add node roles, --node-label and --node-taint flags [#379, #394] - Adds master or worker role to a node, and provides flags to add a set of Labels or Taints to kubelet.
  • Always restart k3s in systemd [#420] - Adds restart=always to k3s service files.
  • Add external database support [#453] - Adds capability for using a MySQL or Postgres database with TLS cert/keys support.
  • Expose Traefik LoadBalancer IP on Ingresses [#534] - Configures Traefik to update the Ingress Resources loadBalancer status.
  • Update to kubernetes v1.14.3 - Upgraded from Kubernetes v1.14.1 [changelog].

Known Issues

  • valuesContent in helm resources fail [#551]

Bug fixes

  • Fixed an issue where k3s may not be configured correctly if br_netfilter is a built-in kernel module [#465]
  • Fixed an issue where k3s kubectl can not find k3s.yaml in a custom install location [#378]
  • Fixed an issue where rootless k3s does not work if /var/lib/cni is missing [#470]
  • Fixed an issue where watch chan error: EOF appears frequently in the logs [#463]
  • Fixed an issue where special characters were not escaped by the installer [#512]
  • Fixed an issue where service IPs were updating even tho no-deploy=servicelb was set [#542]
Assets 16
Loading