hetzner-k3s 0.5.5 → 0.5.6
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Gemfile.lock +1 -1
- data/README.md +2 -2
- data/bin/build.sh +3 -3
- data/lib/hetzner/k3s/cluster.rb +1 -1
- data/lib/hetzner/k3s/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 59601611401c4cb51de78a2890261cd05a1c026479c3e33fcf351f0b3ffb93d1
|
4
|
+
data.tar.gz: 46c62ab747e5a43e61b271c8de150ef4a29ed496128725cf417d950cd351bc49
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 5be97d9b3445445a81fd7f5f4387c2503a10acedb3000acb78473ce8a9d8793149a84a2354a24a6de9996a19eb9288c6989a9fa28d81bf5729b753b144c28d07
|
7
|
+
data.tar.gz: 41e54dc8f26485c5c4ed431301a844a727f31bc6672d9e829f3c95b23d687dcae19eb157017a56f72c3ec3d97303034575c5b353d8a82d17b8c8f56deff17366
|
data/Gemfile.lock
CHANGED
data/README.md
CHANGED
@@ -39,7 +39,7 @@ This will install the `hetzner-k3s` executable in your PATH.
|
|
39
39
|
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):
|
40
40
|
|
41
41
|
```bash
|
42
|
-
docker run --rm -it -v ${PWD}:/cluster -v ${HOME}/.ssh:/tmp/.ssh vitobotta/hetzner-k3s:v0.5.
|
42
|
+
docker run --rm -it -v ${PWD}:/cluster -v ${HOME}/.ssh:/tmp/.ssh vitobotta/hetzner-k3s:v0.5.6 create-cluster --config-file /cluster/test.yaml
|
43
43
|
```
|
44
44
|
|
45
45
|
Replace `test.yaml` with the name of your config file.
|
@@ -109,7 +109,7 @@ If you set `masters.instance_count` to 1 then the tool will create a non highly
|
|
109
109
|
|
110
110
|
You can specify any number of worker node pools for example to have mixed nodes with different specs for different workloads.
|
111
111
|
|
112
|
-
At the moment Hetzner Cloud has four locations: two in Germany (`nbg1`, Nuremberg and `fsn1`,
|
112
|
+
At the moment Hetzner Cloud has four locations: two in Germany (`nbg1`, Nuremberg and `fsn1`, Falkenstein), one in Finland (`hel1`, Helsinki) and one in the USA (`ash`, Ashburn, Virginia). Please note that the Ashburn, Virginia location has just
|
113
113
|
been announced and it's limited to AMD instances for now.
|
114
114
|
|
115
115
|
For the available instance types and their specs, either check from inside a project when adding a server manually or run the following with your Hetzner token:
|
data/bin/build.sh
CHANGED
@@ -6,9 +6,9 @@ set -e
|
|
6
6
|
|
7
7
|
IMAGE="vitobotta/hetzner-k3s"
|
8
8
|
|
9
|
-
docker build -t ${IMAGE}:v0.5.
|
9
|
+
docker build -t ${IMAGE}:v0.5.6 \
|
10
10
|
--platform=linux/amd64 \
|
11
|
-
--cache-from ${IMAGE}:v0.5.
|
11
|
+
--cache-from ${IMAGE}:v0.5.5 \
|
12
12
|
--build-arg BUILDKIT_INLINE_CACHE=1 .
|
13
13
|
|
14
|
-
docker push vitobotta/hetzner-k3s:v0.5.
|
14
|
+
docker push vitobotta/hetzner-k3s:v0.5.6
|
data/lib/hetzner/k3s/cluster.rb
CHANGED
@@ -541,7 +541,7 @@ class Cluster
|
|
541
541
|
end
|
542
542
|
|
543
543
|
def create_load_balancer
|
544
|
-
Hetzner::LoadBalancer.new(hetzner_client:, cluster_name:).create(location
|
544
|
+
Hetzner::LoadBalancer.new(hetzner_client:, cluster_name:).create(location: masters_location, network_id:)
|
545
545
|
end
|
546
546
|
|
547
547
|
def server_configs
|
data/lib/hetzner/k3s/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: hetzner-k3s
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.5.
|
4
|
+
version: 0.5.6
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Vito Botta
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2022-02-
|
11
|
+
date: 2022-02-25 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: bcrypt_pbkdf
|