v0.6.6

• The Linux binary is now statically compiled, so you no longer need to install some dependencies

v0.6.5

• This is a complete rewrite of the tool in Crystal:
  • the tool is even faster than before
  • Crystal allows distribution of proper binaries
  • it is no longer necessary to either set up a Ruby environment of using Docker, like with the previous versions
  • the Ruby version will no longer be maintained.

Upgrading

• The --config-file argument is now called --config
• The create-cluster command is now called create
• The delete-cluster command is now called delete
• The upgrade-cluster command is now called upgrade
• The masters config key has been renamed to masters_pool
• The root level location config key has been moved to the masters_pool section

See the README for more details.

v0.6.4

• Add support for verbose SSH logging with the SSH_DEBUG environment variable

v0.6.3

• Done some refactoring
• Ensured the first master is ready before setting up other masters

v0.6.2

• Added the ability to specify labels and taints for nodes

v0.6.1

• Made some small adjustments to asset filenames and to support installing with Homebrew

v0.6.0

• Add standalone executables for macOS (Intel and ARM) as well as LInux. This way installing a Ruby runtime or using the Docker image is no longer necessary but still available.

v0.5.9

• Ensure the releases command lists all the available k3s releases, not just the most recent ones
• Require one or more networks to configure in the firewall to allow access to the Kubernetes API. In the previous version, access to the Kubernetes API was allowed from any network. Note that this is currently supported only for single master clusters; HA clusters use a load balancer for the Kubernetes API, but the Hetzner firewalls don't support protecting load balancers yet.
• From clusters with k3s version equal or greater than v1.23.6+k3s1, now uses the wireguard-native flannel backend instead of the old wireguard backend (if encryption is enabled in the configuration)
• Update CSI driver to support Kubernetes up to 1.24
• Update System Upgrade Controller to 1.9.1 for k3s updates

v0.5.8

• Ensure the releases command lists all the available k3s releases, not just the most recent ones. This allows for creating clusters with an older version if needed.

v0.5.7

• Allow specifying some commands to run on the servers soon after they are created and before Kubernetes is set up. This can be used to update the OS packages.