hetzner-k3s 0.3.6 → 0.3.7

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: 2b1b2acb7f0649eac91750409418446c2b1ffea2b1b7a32b1f9f8a6fd2d50c5b
4
- data.tar.gz: 457994e28a028e8a1052e20a68ab653bb41fdf5fb88160f43e51b3de49bc8710
3
+ metadata.gz: bb3b106422fe5e298a81ffe6b913593ff20a7cdbc7e658012f31f707b1f5732e
4
+ data.tar.gz: 5face1d08a752c26c93da8c5638c947b711d9fff4428c98f163f78bc3e206de8
5
5
  SHA512:
6
- metadata.gz: 743edefe6fdaa9ebf9dc2236e4ce672f44d10bcbe954bda7a1560c4166cacf12824eb6c994dfe635543746c402696d981a22224852bb25a7df7558c81bdbbff3
7
- data.tar.gz: 506488a2edac4c9e7b68d09e8b8dd8a970993dc8a87ba7d6bf3200856f4384ebe90362ea2fe337e2cdb4f43cb951b7c79c2a9a26154ed278b1704c369b88e85a
6
+ metadata.gz: 389f431593261968ac05127c93c9f49e3aee71836e4240183e74ba5292daae53c5ab1a985bbcef3015fff54957b9072bb6bb99ce6837f78acacfe7915dbeed94
7
+ data.tar.gz: 4fd8bd35216ab0c1c9204295c7a8c6009989b0af452c743da808310de9367c5461d07eb1af50e1059ace49026e278c7c1c11aaeb9ad139cedfbbdf18ce1bf8ca
data/Dockerfile CHANGED
@@ -3,6 +3,9 @@ FROM ruby:2.7.4-alpine
3
3
  RUN apk update --no-cache \
4
4
  && apk add build-base git openssh-client
5
5
 
6
+ COPY Gemfile Gemfile
7
+ COPY hetzner-k3s.gemspec hetzner-k3s.gemspec
8
+
6
9
  RUN gem install hetzner-k3s
7
10
 
8
11
  COPY entrypoint.sh /entrypoint.sh
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- hetzner-k3s (0.3.6)
4
+ hetzner-k3s (0.3.7)
5
5
  bcrypt_pbkdf
6
6
  ed25519
7
7
  http
data/README.md CHANGED
@@ -38,7 +38,7 @@ This will install the `hetzner-k3s` executable in your PATH.
38
38
  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):
39
39
 
40
40
  ```bash
41
- docker run --rm -it -v ${PWD}:/cluster -v ${HOME}/.ssh:/tmp/.ssh vitobotta/hetzner-k3s create-cluster --config-file /cluster/test.yaml
41
+ docker run --rm -it -v ${PWD}:/cluster -v ${HOME}/.ssh:/tmp/.ssh vitobotta/hetzner-k3s:v0.3.7 create-cluster --config-file /cluster/test.yaml
42
42
  ```
43
43
 
44
44
  Replace `test.yaml` with the name of your config file.
@@ -227,6 +227,9 @@ Once the cluster is ready you can create persistent volumes out of the box with
227
227
 
228
228
  ## changelog
229
229
 
230
+ - 0.3.7
231
+ - Ensure that the cluster name only contains lowercase letters, digits and dashes for compatibility with the cloud controller manager
232
+
230
233
  - 0.3.6
231
234
  - Retry SSH commands when IO errors occur
232
235
 
@@ -110,7 +110,8 @@ module Hetzner
110
110
  end
111
111
 
112
112
  def validate_cluster_name
113
- errors << "Cluster name is an invalid format" unless configuration["cluster_name"] =~ /\A([A-Za-z0-9\-\_]+)\Z/
113
+ errors << "Cluster name is an invalid format (only lowercase letters, digits and dashes are allowed)" unless configuration["cluster_name"] =~ /\A[a-z\d-]+\z/
114
+ errors << "Ensure that the cluster name starts with a normal letter" unless configuration["cluster_name"] =~ /\A[a-z]+.*\z/
114
115
  end
115
116
 
116
117
  def validate_kubeconfig_path
@@ -1,5 +1,5 @@
1
1
  module Hetzner
2
2
  module K3s
3
- VERSION = "0.3.6"
3
+ VERSION = "0.3.7"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: hetzner-k3s
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.6
4
+ version: 0.3.7
5
5
  platform: ruby
6
6
  authors:
7
7
  - Vito Botta