From a8d7e48f91bc4019a813cfd5a3c7ddba228e5151 Mon Sep 17 00:00:00 2001
From: mysticaltech <518555+mysticaltech@users.noreply.github.com>
Date: Fri, 8 Nov 2024 00:04:27 +0000
Subject: [PATCH 1/2] Update Terraform documentation
---
docs/terraform.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/terraform.md b/docs/terraform.md
index c4eef44f..21bc2e15 100644
--- a/docs/terraform.md
+++ b/docs/terraform.md
@@ -173,7 +173,7 @@
| [ingress\_max\_replica\_count](#input\_ingress\_max\_replica\_count) | Number of maximum replicas per ingress controller. Used for ingress HPA. Must be higher than number of replicas. | `number` | `10` | no |
| [ingress\_replica\_count](#input\_ingress\_replica\_count) | Number of replicas per ingress controller. 0 means autodetect based on the number of agent nodes. | `number` | `0` | no |
| [ingress\_target\_namespace](#input\_ingress\_target\_namespace) | The namespace to deploy the ingress controller to. Defaults to ingress name. | `string` | `""` | no |
-| [initial\_k3s\_channel](#input\_initial\_k3s\_channel) | Allows you to specify an initial k3s channel. | `string` | `"stable"` | no |
+| [initial\_k3s\_channel](#input\_initial\_k3s\_channel) | Allows you to specify an initial k3s channel. | `string` | `"v1.30"` | no |
| [install\_k3s\_version](#input\_install\_k3s\_version) | Allows you to specify the k3s version (Example: v1.29.6+k3s2). Supersedes initial\_k3s\_channel. | `string` | `""` | no |
| [k3s\_agent\_kubelet\_args](#input\_k3s\_agent\_kubelet\_args) | Kubelet args for agent nodes. | `list(string)` | `[]` | no |
| [k3s\_autoscaler\_kubelet\_args](#input\_k3s\_autoscaler\_kubelet\_args) | Kubelet args for autoscaler nodes. | `list(string)` | `[]` | no |
From 89fd80428122d77c79a967237669b98ff70b6f55 Mon Sep 17 00:00:00 2001
From: Felix
Date: Sat, 9 Nov 2024 20:22:59 +0100
Subject: [PATCH 2/2] Updated maximum volume size to 10240
---
agents.tf | 4 ++--
kube.tf.example | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/agents.tf b/agents.tf
index ba8b6437..0c3e4534 100644
--- a/agents.tf
+++ b/agents.tf
@@ -130,7 +130,7 @@ resource "null_resource" "agents" {
}
resource "hcloud_volume" "longhorn_volume" {
- for_each = { for k, v in local.agent_nodes : k => v if((v.longhorn_volume_size >= 10) && (v.longhorn_volume_size <= 10000) && var.enable_longhorn) }
+ for_each = { for k, v in local.agent_nodes : k => v if((v.longhorn_volume_size >= 10) && (v.longhorn_volume_size <= 10240) && var.enable_longhorn) }
labels = {
provisioner = "terraform"
@@ -146,7 +146,7 @@ resource "hcloud_volume" "longhorn_volume" {
}
resource "null_resource" "configure_longhorn_volume" {
- for_each = { for k, v in local.agent_nodes : k => v if((v.longhorn_volume_size >= 10) && (v.longhorn_volume_size <= 10000) && var.enable_longhorn) }
+ for_each = { for k, v in local.agent_nodes : k => v if((v.longhorn_volume_size >= 10) && (v.longhorn_volume_size <= 10240) && var.enable_longhorn) }
triggers = {
agent_id = module.agents[each.key].id
diff --git a/kube.tf.example b/kube.tf.example
index 8ce0ba9b..4cb84c5d 100644
--- a/kube.tf.example
+++ b/kube.tf.example
@@ -209,7 +209,7 @@ module "kube-hetzner" {
taints = [],
count = 1
- # In the case of using Longhorn, you can use Hetzner volumes instead of using the node's own storage by specifying a value from 10 to 10000 (in GB)
+ # In the case of using Longhorn, you can use Hetzner volumes instead of using the node's own storage by specifying a value from 10 to 10240 (in GB)
# It will create one volume per node in the nodepool, and configure Longhorn to use them.
# Something worth noting is that Volume storage is slower than node storage, which is achieved by not mentioning longhorn_volume_size or setting it to 0.
# So for something like DBs, you definitely want node storage, for other things like backups, volume storage is fine, and cheaper.
@@ -455,7 +455,7 @@ module "kube-hetzner" {
# After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.
# Also, you can choose to use a Hetzner volume with Longhorn. By default, it will use the nodes own storage space, but if you add an attribute of
- # longhorn_volume_size (⚠️ not a variable, just a possible agent nodepool attribute) with a value between 10 and 10000 GB to your agent nodepool definition, it will create and use the volume in question.
+ # longhorn_volume_size (⚠️ not a variable, just a possible agent nodepool attribute) with a value between 10 and 10240 GB to your agent nodepool definition, it will create and use the volume in question.
# See the agent nodepool section for an example of how to do that.
# To disable Hetzner CSI storage, you can set the following to "true", default is "false".