hetzner-k3s 0.3.3 → 0.3.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4f45064341000a4cf3a3ec6aef60c2b26eb95758e3c0e1d16c87740b8e549834
-  data.tar.gz: 0ec683973e5c27811c8f9a2d82804ce3721d9a93137c46d15087f8e06a9fe4b2
+  metadata.gz: 362875671a52928fd320f24cb0ef38728fe85f5395282f8d9df9550c8531162f
+  data.tar.gz: b873e5f6823a443f48577a5126c20f2b5b4db3a1e2c4fb791af059718cbf39a0
 SHA512:
-  metadata.gz: 7ac95d48d017c7997c3e20b7dd3d5160bf5188a4bff9144efc382606bf2d83462221287b8ba9c16ff62b5f3687486f310f042add4c50f06228e0f2da4afb63db
-  data.tar.gz: bd2caff255115cdd82582b5c143249ca92983d4232ab77ba03fe5d4719fc812dfb3af7b8617fc6adaa0c9093ef66c0b6f1cdbdee5f60c25e5f2f819fc6fa8f0b
+  metadata.gz: ecee605e0fc079b62a3cd6af152d30dbdb7ea5cb4785f8a2bcda6218996f7a86bcdcac23f0010d61f6a16e7964f6e587f0c6e0a54ba41c790af15c6490b3ecdb
+  data.tar.gz: 476d5dd9a39dfd45258cd32d208e3e15d6f79f6cf326d482694e6b6311259731ebb090965fc1dcefbb216ee25cd5e01cbdfb36d5a65bafa9a80e56eb047e3d7c

data/Dockerfile

@@ -0,0 +1,11 @@
+FROM ruby:2.7.4-alpine
+
+RUN apk update --no-cache \
+  && apk add build-base git openssh-client
+
+RUN gem install hetzner-k3s
+
+COPY entrypoint.sh /entrypoint.sh
+
+ENTRYPOINT ["/entrypoint.sh"]
+

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    hetzner-k3s (0.3.3)
+    hetzner-k3s (0.3.4)
       bcrypt_pbkdf
       ed25519
       http

data/README.md

@@ -33,6 +33,16 @@ gem install hetzner-k3s
 
 This will install the `hetzner-k3s` executable in your PATH.
 
+### With Docker
+
+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 create-cluster --config-file /cluster/test.yaml
+```
+
+Replace `test.yaml` with the name of your config file.
+
 ## Creating a cluster
 
 The tool requires a simple configuration file in order to create/upgrade/delete clusters, in the YAML format like in the example below:
@@ -60,6 +70,9 @@ worker_node_pools:
 
 It should hopefully be self explanatory; you can run `hetzner-k3s releases` to see a list of the available releases from the most recent to the oldest available.
 
+If you are using Docker, then set `kubeconfig_path` to `/cluster/kubeconfig` so that the kubeconfig is created in the same directory where your config file is.
+
+
 If you set `masters.instance_count` to 1 then the tool will create a non highly available control plane; for production clusters you may want to set it to a number greater than 1. This number must be odd to avoid split brain issues with etcd and the recommended number is 3.
 
 You can specify any number of worker node pools for example to have mixed nodes with different specs for different workloads.
@@ -214,6 +227,9 @@ Once the cluster is ready you can create persistent volumes out of the box with
 
 ## changelog
 
+- 0.3.4
+  - Added Docker support
+
 - 0.3.3
   - Add some gems required on Linux
 

data/entrypoint.sh

@@ -0,0 +1,12 @@
+#!/bin/sh
+
+cp -R /tmp/.ssh /root/.ssh
+chmod 700 /root/.ssh
+chmod 600 /root/.ssh/*
+chmod 644 /root/.ssh/*.pub
+
+eval $(ssh-agent -s) 2&>1  > /dev/null
+
+ssh-add ~/.ssh/* 2&>1  > /dev/null
+
+hetzner-k3s "$@"

data/lib/hetzner/k3s/version.rb

@@ -1,5 +1,5 @@
 module Hetzner
   module K3s
-    VERSION = "0.3.3"
+    VERSION = "0.3.4"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: hetzner-k3s
 version: !ruby/object:Gem::Version
-  version: 0.3.3
+  version: 0.3.4
 platform: ruby
 authors:
 - Vito Botta
@@ -121,6 +121,7 @@ files:
 - ".rspec"
 - ".travis.yml"
 - CODE_OF_CONDUCT.md
+- Dockerfile
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
@@ -129,6 +130,7 @@ files:
 - bin/console
 - bin/setup
 - cluster_config.yaml.example
+- entrypoint.sh
 - exe/hetzner-k3s
 - hetzner-k3s.gemspec
 - lib/hetzner.rb