-
-
Notifications
You must be signed in to change notification settings - Fork 147
Home
Vito Botta edited this page Feb 8, 2022
·
4 revisions
-
0.5.2, Feb 8, 2022
- Ensure that in a HA cluster the nodes connect to the load balancer for the API server, instead of the first master
-
0.5.1
- Each node pool gets its own placement group. This is to minimize issues due to the max 10 nodes limitation for a single node group. A validation has also been added to limit pools to 10 nodes each because of this.
-
0.5.0
- Allow installing additional packages when creating the servers
- Allow enabling ipsec encryption
-
0.4.9
- Ensure the program always exits with exit code 1 if the config file fails validation
- Upgrade System Upgrade Controller to 0.8.1
- Remove dependency on unmaintained gem k8s-ruby
- Make the gem compatible with Ruby 3.1.0
-
0.4.8
- Increase timeout with API requests to 30 seconds
- Limit number of retries for API requests to 3
- Ensure all version tags are listed for k3s (thanks @janosmiko)
-
0.4.7
- Made it possible to specify a custom image/snapshot for the servers
-
0.4.6
- Added a check to abort gracefully when for some reason one or more servers are not created, for example due to temporary problems with the Hetzner API.
-
0.4.5
- Fix network creation (bug introduced in the previous version)
-
0.4.4
- Add support for the new Ashburn, Virginia (USA) location
- Automatically use a placement group so that the instances are all created on different physical hosts for high availability
-
0.4.3
- Fix an issue with SSH key creation
-
0.4.2
- Update Hetzner CSI driver to v1.6.0
- Update System Upgrade Controller to v0.8.0
-
0.4.1
- Allow to optionally specify the path of the private SSH key
- Set correct permissions for the kubeconfig file
- Retry fetching manifests a few times to allow for temporary network issues
- Allow to optionally schedule workloads on masters
- Allow clusters with no worker node pools if scheduling is enabled for the masters
-
0.4.0
- Ensure the masters are removed from the API load balancer before deleting the load balancer
- Ensure the servers are removed from the firewall before deleting it
- Allow using an environment variable to specify the Hetzner token
- Allow restricting SSH access to the nodes to specific networks
- Do not open the port 6443 on the nodes if a load balancer is created for an HA cluster
-
0.3.9
- Add command "version" to print the version of the tool in use
-
0.3.8
- Fix: added a check on a label to ensure that only servers that belong to the cluster are deleted from the project
-
0.3.7
- Ensure that the cluster name only contains lowercase letters, digits and dashes for compatibility with the cloud controller manager
-
0.3.6
- Retry SSH commands when IO errors occur
-
0.3.5
- Add descriptions for firewall rules
-
0.3.4
- Added Docker support
-
0.3.3
- Add some gems required on Linux
-
0.3.2
- Configure DNS to use Cloudflare's resolver instead of Hetzner's, since Hetzner's resolvers are not always reliable
-
0.3.1
- Allow enabling/disabling the host key verification
-
0.3.0
- Handle case when an SSH key with the given fingerprint already exists in the Hetzner project
- Handle a timeout of 5 seconds for requests to the Hetzner API
- Retry waiting for server to be up when timeouts/host-unreachable errors occur
- Ignore known_hosts entry to prevent errors when recreating servers with IPs that have been used previously
-
0.2.0
- Allow mixing servers of different series Intel/AMD