Skip to content

Releases: k3s-io/k3s

Release v0.2.0

09 Mar 02:46
2771ae1
Compare
Choose a tag to compare

Release v0.2.0

Release v0.2.0 of k3s adds several important enhancements and addresses numerous bugs found by our community. Many of these improvements are the direct result of community members opening issues, submitting PRs, and testing fixes. A huge thank you to the community for your support and involvement! Keep it coming!

Features and Enhancements

  • Support arbitrary CRI implementations [#107] - Users can now configure k3s to use cri-o and other CRI implementations that are not packaged into k3s.
  • Support for preloading images [#92] - Users can now have node agents load docker images from a location on the host at startup, eliminating the need to pull images from a remote location.
  • Upgrade to Kubernetes v1.13.4 [#95] - Update to the latest release of Kubernetes.
  • Support k3s on Rancher [#69] - Users can now import k3s clusters into Rancher (supported in Rancher v2.2.0-rc3 and later).
  • Support agent options in server command [#73] - Users can now set any of the options available to agents when starting the k3s server node.
  • Support the ability to run k3s as non-root user [#38] - User can now run the k3s server as a non-root user.
  • Support the ability to read node token from a file [#98] - Users can now have the node-agent read its token from a file rather than passing it as a string.

Bug fixes

  • Fixed an issue where preloaded deployment manifests fail to deploy if no namespace is specified #151
  • Fixed an issue where changes to helm chart values or values.yaml aren't always triggering an upgrade #187
  • Fixed an issue where nodes with uppercase hostnames hang indefinitely #160
  • Fixed an issue where containerd log level environment variable is not respected #188
  • Fixed an issue where node-token path doesn't resolve for root user in agent scripts #189
  • Fixed an issue where traefik is not listed in the --no-deploy flag's help text #186
  • Fixed an issue where changing cluster CIDR was not possible #93
  • Fixed an issue where k3s systemd service should wait until the server is ready #57
  • Fixed an issue where test volume mount e2e fails for k3s image #45
  • Fixed an issue where component status is not accurate #126
  • Fixed an issue where install script fails if wget is not available #48
  • Added the ability to dynamically install the latest release of k3s #47

v0.2.0-rc6: Merge pull request #184 from ibuildthecloud/default-ns

07 Mar 20:07
2771ae1
Compare
Choose a tag to compare
Assign default namespace if not set in manifests

v0.2.0-rc5: Merge pull request #161 from aaliddell/master

05 Mar 19:54
10be950
Compare
Choose a tag to compare
Enforce lower case hostname for node

v0.2.0-rc4: Merge pull request #141 from juliens/preload-images

05 Mar 00:15
4f13bd6
Compare
Choose a tag to compare
preload a docker image on the k3s node agents

v0.2.0-rc3: Merge pull request #148 from ibuildthecloud/revert

04 Mar 20:20
6de915d
Compare
Choose a tag to compare
Revert "Enable systemd ready notification for k3s server"

v0.1.0: Initial Release

26 Feb 05:08
Compare
Choose a tag to compare
Fix asset lookup of HOME directory

Return the directory name if assets are located in HOME, so we can
properly set the PATH for binary lookup.

v0.1.0-rc8

24 Feb 19:02
Compare
Choose a tag to compare
Bump scripts to rc6

v0.1.0-rc7

24 Feb 05:45
Compare
Choose a tag to compare
v0.1.0-rc7 Pre-release
Pre-release
Set /proc/sys/net/ipv4/ip_forward on agent start

v0.1.0-rc6

23 Feb 02:59
Compare
Choose a tag to compare
Disable watch caching, not needed for sqlite

v0.1.0-rc5

19 Feb 17:54
Compare
Choose a tag to compare
Move default config location to /etc/rancher/k3s/k3s.yaml