From 56ff30199d879e416d0efcd5a9b735ddf43b72ba Mon Sep 17 00:00:00 2001 From: Michael Karbowiak Date: Mon, 2 May 2022 16:03:15 +0200 Subject: [PATCH] Make Kured version changeable --- README.md | 7 ++++--- locals.tf | 2 +- terraform.tfvars.example | 8 +++++--- variables.tf | 6 ++++++ 4 files changed, 16 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 6415be5..d9fb2b3 100644 --- a/README.md +++ b/README.md @@ -54,12 +54,13 @@ Follow those simple steps, and your world's cheapest Kube cluster will be up and First and foremost, you need to have a Hetzner Cloud account. You can sign up for free [here](https://hetzner.com/cloud/). -Then you'll need to have [terraform](https://learn.hashicorp.com/tutorials/terraform/install-cli), [kubectl](https://kubernetes.io/docs/tasks/tools/) cli, and [hcloud]() the Hetzner cli. The easiest way is to use the [homebrew](https://brew.sh/) package manager to install them (available on Linux, Mac, and Windows Linux Subsystem). +Then you'll need to have [terraform](https://learn.hashicorp.com/tutorials/terraform/install-cli), [kubectl](https://kubernetes.io/docs/tasks/tools/) cli, [helm]() Helm and [hcloud]() the Hetzner cli. The easiest way is to use the [homebrew](https://brew.sh/) package manager to install them (available on Linux, Mac, and Windows Linux Subsystem). ```sh brew install terraform brew install kubectl brew install hcloud +brew install helm ``` @@ -205,7 +206,7 @@ It is easy to use Kube-Hetzner as a Terraform module. To do so: ``` terraform module "kube-hetzner" { source = "kube-hetzner/kube-hetzner/hcloud" - + # insert the required variables here found in terraform.tfvars.example } ``` @@ -285,4 +286,4 @@ Code contributions are very much **welcome**. [issues-url]: https://github.com/mysticaltech/kube-hetzner/issues [license-shield]: https://img.shields.io/github/license/mysticaltech/kube-hetzner.svg?style=for-the-badge [license-url]: https://github.com/mysticaltech/kube-hetzner/blob/master/LICENSE.txt -[product-screenshot]: https://github.com/kube-hetzner/kube-hetzner/raw/master/.images/kubectl-pod-all-17022022.png \ No newline at end of file +[product-screenshot]: https://github.com/kube-hetzner/kube-hetzner/raw/master/.images/kubectl-pod-all-17022022.png diff --git a/locals.tf b/locals.tf index 797f230..1de9764 100644 --- a/locals.tf +++ b/locals.tf @@ -13,7 +13,7 @@ locals { ccm_version = var.hetzner_ccm_version != null ? var.hetzner_ccm_version : data.github_release.hetzner_ccm.release_tag csi_version = var.hetzner_csi_version != null ? var.hetzner_csi_version : data.github_release.hetzner_csi.release_tag - kured_version = data.github_release.kured.release_tag + kured_version = var.kured_version != null ? var.kured_version : data.github_release.kured.release_tag common_commands_install_k3s = [ "set -ex", diff --git a/terraform.tfvars.example b/terraform.tfvars.example index 29fc1a3..fceaafc 100644 --- a/terraform.tfvars.example +++ b/terraform.tfvars.example @@ -24,9 +24,9 @@ network_region = "eu-central" # change to `us-east` if location is ash # Of course, you can choose any number of nodepools you want, with the location you want. The only constraint on the location is that you need to stay in the same network region, Europe, or the US. # For the server type, the minimum instance supported is cpx11 (just a few cents more than cx11); see https://www.hetzner.com/cloud. -# IMPORTANT: Before you create your cluster, you can do anything you want with the nodepools, but you need at least one of each control plane and agent. +# IMPORTANT: Before you create your cluster, you can do anything you want with the nodepools, but you need at least one of each control plane and agent. # Once the cluster is up and running, you can change nodepool count and even set it to 0 (in the case of the first control-plane nodepool, the minimum is 1), -# you can also rename it (if the count is 0), but do not remove a nodepool from the list. +# you can also rename it (if the count is 0), but do not remove a nodepool from the list. # The only nodepools that are safe to remove from the list when you edit it are at the end of the lists. That is due to how subnets and IPs get allocated (FILO). # You can, however, freely add other nodepools at the end of each list if you want! The maximum number of nodepools you can create combined for both lists is 255. @@ -107,6 +107,8 @@ load_balancer_location = "fsn1" # hetzner_ccm_version = "" # hetzner_csi_version = "" +# If you want to specify the Kured version, set it below - otherwise it'll use the latest version available +# kured_version = "" # We give you the possibility to use letsencrypt directly with Traefik because it's an easy setup, however it's not optimal, # as the free version of Traefik causes a little bit of downtime when when the certificates get renewed. For proper SSL management, @@ -175,4 +177,4 @@ load_balancer_location = "fsn1" # If you want to disable the automatic use of placement group "spread". See https://docs.hetzner.com/cloud/placement-groups/overview/ # That may be useful if you need to deploy more than 500 nodes! The default is "false". -# placement_group_disable = true \ No newline at end of file +# placement_group_disable = true diff --git a/variables.tf b/variables.tf index 6b7fba8..6ad438e 100644 --- a/variables.tf +++ b/variables.tf @@ -65,6 +65,12 @@ variable "hetzner_csi_version" { description = "Version of Container Storage Interface driver for Hetzner Cloud" } +variable "kured_version" { + type = string + default = null + description = "Version of Kured" +} + variable "traefik_enabled" { type = bool default = true