hetzner-k3s

• Make it possible to customize the subnet

• Fixed: now it is possible to specify the Hetzner Cloud token in the environment variable HCLOUD_TOKEN instead of the config file. This makes it possible to safely commit the config file to a repository without leaking the token
• Fixed: there was an issue preventing cluster upgrades due to a bug in the comparison of the new k3s version with the current

• Makes it possible to use keys with old SHA1 crypto on Redhat system, until the upstream ssh2 library is updated

• As a temporary workaround, configures new servers with Ubuntu 22.04 (and others that have deprecated SHA1 for SSH keys) to use SSH keys with old crypto. This is a workaround until libssh2 is updated upstream.

• Fixed an issue with autoscaling when using an openSUSE MicroOS snapshot instead of a default OS image

• Improvement: it is now possible to use a custom snapshot instead of one of the default OS images. This makes it now possible to use an alternative OS like openSuSE MicroOS which is not supported by Hetzner directly. See the README for details and limitations.

• Fixed an issue preventing creation of a cluster with an OS image other than Ubuntu
• Changed default image to Ubuntu 22.04
• Fixed an issue with cluster creation hanging if one or more nodes were not attached to the private network yet
• Upgraded Cluster Autoscaler to 1.26.1

• Allow using an SSH agent by setting the new use_ssh_agent config setting to true. This solves problems with some SSH keys and also makes it possible to use SSH keys protected with a passphrase

• Allow the Cluster Autoscaler to be scheduled on a master even when the masters are tainted not to schedule other pods

• Implemented autoscaling 🎉

• Cache the k3s releases in a temporary file instead of a file in the current directory

• Fixed an issue with allowed networks validation

• Made it possible to specify a relative path for the kubeconfig
• The tool now halts execution when a shell command fails

• Add support for the us-west region

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

• 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.

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

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

• Added the ability to specify labels and taints for nodes

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