hetzner-k3s 0.4.2 → 0.4.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 703675cd5cbfeb28c857486046b88a1202835316b4522ac3b964c42479ca91e9
-  data.tar.gz: d496229db7199e5d72bf19e5534ce83c7235ffe91eb93aec2151435d4c3a9c2c
+  metadata.gz: c3e7bedd3a695b38522a25598d9d0523bee9e5120aea6e76c462ba91dc8f3f12
+  data.tar.gz: d54f24ebe59f8b0354c74fdacff6f747169b288eddb99f070456f147523a07b4
 SHA512:
-  metadata.gz: 75f9af0a29e2e34e7e4fd703ee1a98f2a2e2b9cd8143783583f74ce26427b1bbfbf53930f258b1a5fc9faf9fe1e1a84e7f15f5c92122ecfd1b4ae6ae7913031e
-  data.tar.gz: b89c51f47038eca49083cf8936d7cc4927a8edbe9fe41582d834dd546a2be8d5b80ef03bf3bf0bce7605637e35445e153c1c72bf206ed58df9632c4a245d9f3b
+  metadata.gz: 36c460db4001ba080ef27dec517c4c44ce853a75935fee7d0fc5e4a13d689a5e812d762ec842a22503ac07d555a24be545293db9bb838ddcb7d27cd1866d9a1e
+  data.tar.gz: 2e8f67ca3c74292b7ad3c3a2098b1a4c8d096b1cb01677e8cc94ae199ee4b0df25eb869d2400b32451da6475a7518c7265cd1b70ec6bb0090e25b76047a03e4e

data/README.md

@@ -38,7 +38,7 @@ This will install the `hetzner-k3s` executable in your PATH.
 Alternatively, if you don't want to set up a Ruby runtime but have Docker installed, you can use a container. Run the following from inside the directory where you have the config file for the cluster (described in the next section):
 
 ```bash
-docker run --rm -it -v ${PWD}:/cluster -v ${HOME}/.ssh:/tmp/.ssh vitobotta/hetzner-k3s:v0.4.1 create-cluster --config-file /cluster/test.yaml
+docker run --rm -it -v ${PWD}:/cluster -v ${HOME}/.ssh:/tmp/.ssh vitobotta/hetzner-k3s:v0.4.2 create-cluster --config-file /cluster/test.yaml
 ```
 
 Replace `test.yaml` with the name of your config file.
@@ -78,7 +78,7 @@ If you are using Docker, then set `kubeconfig_path` to `/cluster/kubeconfig` so
 
 If you don't want to specify the Hetzner token in the config file (for example if you want to use the tool with CI), then you can use the `HCLOUD_TOKEN` environment variable instead, which has predecence.
 
-**Important**: The tool assignes the label `cluster` to each server it creates, with the clsuter name you specify in the config file, as the value. So please ensure you don't create unrelated servers in the same project having
+**Important**: The tool assignes the label `cluster` to each server it creates, with the cluster name you specify in the config file, as the value. So please ensure you don't create unrelated servers in the same project having
 the label `cluster=<cluster name>`, because otherwise they will be deleted if you delete the cluster. I recommend you create a separate Hetzner project for each cluster, see note at the end of this README for more details.
 
 
@@ -241,6 +241,9 @@ I recommend that you create a separate Hetzner project for each cluster, because
 
 ## changelog
 
+- 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

data/bin/build.sh

@@ -6,9 +6,9 @@ set -e
 
 IMAGE="vitobotta/hetzner-k3s"
 
-docker build -t ${IMAGE}:v0.4.2 \
+docker build -t ${IMAGE}:v0.4.3 \
   --platform=linux/amd64 \
-  --cache-from ${IMAGE}:v0.4.1 \
+  --cache-from ${IMAGE}:v0.4.2 \
   --build-arg BUILDKIT_INLINE_CACHE=1 .
 
 docker push vitobotta/hetzner-k3s:v0.4.2

data/lib/hetzner/infra/ssh_key.rb

@@ -55,7 +55,7 @@ module Hetzner
       def ssh_key_config
         {
           name: cluster_name,
-          public_ssh_key: public_ssh_key
+          public_key: public_ssh_key
         }
       end
 

data/lib/hetzner/k3s/version.rb

@@ -1,5 +1,5 @@
 module Hetzner
   module K3s
-    VERSION = "0.4.2"
+    VERSION = "0.4.3"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: hetzner-k3s
 version: !ruby/object:Gem::Version
-  version: 0.4.2
+  version: 0.4.3
 platform: ruby
 authors:
 - Vito Botta
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2021-10-03 00:00:00.000000000 Z
+date: 2021-10-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor