hetzner-k3s 0.5.1 → 0.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: c236d440e3e99f656c62b8ced99ac899199e435ca41e9675c4adeb326a87c5d8
4
- data.tar.gz: fd8da58d3c4cc3b54018c1ff261f8606391e8f524b974660fc5984fcd10397f7
3
+ metadata.gz: 45de69f63ea8c675489cc385a2860c798923f42af6e9fa4af791042ae57aa7dd
4
+ data.tar.gz: 778c30870784ee1d0f9bcb4b102639bc8f295faa60eca8bb9d0ef7ff56905c9a
5
5
  SHA512:
6
- metadata.gz: 8ebe7779e0f79ec500c1e0d230212cd568ef62e94a3dd2d936214f03f48baf8fc937a683b7bf4478b66a3dc0a7b02ee001a6fe3e542ad401f0add4ee27a68b03
7
- data.tar.gz: dae117d8d1e3babf392814baf372009d1558113673a4968b7526a0a4e3a06b8eea034edaa11452047286721efc2a37af3e8214f2dbeafde73d864493feae5626
6
+ metadata.gz: 301590287388f2c512e66504558d88fe7e31237c0525a37f96ca5f090190421a2841c66a59f1be2b5a45c632f5ad6799ecab4894058335387fbdce6927b3c7a3
7
+ data.tar.gz: 3715433adfe0f43889f33962844d54d30017b1a85c5c9ff0a6c21b70980e3b01dbdb431020441404654845d46044643725b8558dc6c0fff49992ab6297ebed71
data/README.md CHANGED
@@ -25,7 +25,7 @@ All that is needed to use this tool is
25
25
 
26
26
  ## Installation
27
27
 
28
- Once you have the Ruby runtime up and running (2.7.2 or newer), you just need to install the gem:
28
+ Once you have the Ruby runtime up and running (3.1.0 or newer), you just need to install the gem:
29
29
 
30
30
  ```bash
31
31
  gem install hetzner-k3s
@@ -257,6 +257,9 @@ I recommend that you create a separate Hetzner project for each cluster, because
257
257
 
258
258
  ## changelog
259
259
 
260
+ - 0.5.2
261
+ - Ensure that in a HA cluster the nodes connect to the load balancer for the API server, instead of the first master
262
+
260
263
  - 0.5.1
261
264
  - 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.
262
265
 
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.1 \
9
+ docker build -t ${IMAGE}:v0.5.2 \
10
10
  --platform=linux/amd64 \
11
- --cache-from ${IMAGE}:v0.5.0 \
11
+ --cache-from ${IMAGE}:v0.5.1 \
12
12
  --build-arg BUILDKIT_INLINE_CACHE=1 .
13
13
 
14
- docker push vitobotta/hetzner-k3s:v0.5.1
14
+ docker push vitobotta/hetzner-k3s:v0.5.2
@@ -188,7 +188,7 @@ class Cluster
188
188
  end
189
189
 
190
190
  def master_script(master)
191
- server = master == first_master ? ' --cluster-init ' : " --server https://#{first_master_private_ip}:6443 "
191
+ server = master == first_master ? ' --cluster-init ' : " --server https://#{api_server_ip}:6443 "
192
192
  flannel_interface = find_flannel_interface(master)
193
193
  flannel_ipsec = enable_ipsec_encryption ? ' --flannel-backend=ipsec ' : ' '
194
194
 
@@ -2,6 +2,6 @@
2
2
 
3
3
  module Hetzner
4
4
  module K3s
5
- VERSION = '0.5.1'
5
+ VERSION = '0.5.2'
6
6
  end
7
7
  end
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.1
4
+ version: 0.5.2
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-06 00:00:00.000000000 Z
11
+ date: 2022-02-08 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bcrypt_pbkdf