From a156fb5fc549d0da9d2c0898e280c6ca97d943eb Mon Sep 17 00:00:00 2001 From: Salar Nasiri Date: Mon, 3 Feb 2025 00:52:30 +0330 Subject: [PATCH 1/6] Update Masters_in_different_locations.md Fix typo --- docs/Masters_in_different_locations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Masters_in_different_locations.md b/docs/Masters_in_different_locations.md index e6b60891..9aa4269a 100644 --- a/docs/Masters_in_different_locations.md +++ b/docs/Masters_in_different_locations.md @@ -10,7 +10,7 @@ If you already have a cluster with a single master or three masters in the same Before you begin, make sure to back up all your applications and data! This is crucial. While the migration process is relatively simple, there is always some level of risk involved. -- [ ] Set the `instance_type` for the masters pool to 3 if your cluster currently has only one master. +- [ ] Set the `instance_count` for the masters pool to 3 if your cluster currently has only one master. - [ ] Update the `locations` setting for the masters pool to include `fns1`, `hel1`, and `nbg1` like this: ```yaml From e5227829b0c75545fde52efe3a1372b2dc06a64e Mon Sep 17 00:00:00 2001 From: Vito Botta Date: Mon, 3 Feb 2025 19:59:30 +0200 Subject: [PATCH 2/6] Update Deleting_a_cluster.md --- docs/Deleting_a_cluster.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/Deleting_a_cluster.md b/docs/Deleting_a_cluster.md index 876e6772..cb3d00be 100644 --- a/docs/Deleting_a_cluster.md +++ b/docs/Deleting_a_cluster.md @@ -8,5 +8,6 @@ hetzner-k3s delete --config cluster_config.yaml This will delete all the resources in the Hetzner Cloud project created by `hetzner-k3s` directly. -**NOTE:** at the moment instances created by the cluster autoscaler, as well as load balancers and persistent volumes created by deploying your applications must be deleted manually. This may be addressed in a future release. +**NOTE:** at the load balancers and persistent volumes created by deploying your applications must be deleted manually. This may be addressed in a future release. +Also note that being able to delete a cluster requires setting `protect_against_deletion` to `true` and that you enter the name of the cluster when you run the `delete` command to confirm that you really want to delete it. These measures are to prevent accidental deletion of a cluster that is jot meant to be deleted. \ No newline at end of file From aa0f1366f770c3ea6b6eb6eebca275bec07c7ac8 Mon Sep 17 00:00:00 2001 From: Vito Botta Date: Mon, 3 Feb 2025 19:59:41 +0200 Subject: [PATCH 3/6] Update Deleting_a_cluster.md --- docs/Deleting_a_cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Deleting_a_cluster.md b/docs/Deleting_a_cluster.md index cb3d00be..31151700 100644 --- a/docs/Deleting_a_cluster.md +++ b/docs/Deleting_a_cluster.md @@ -8,6 +8,6 @@ hetzner-k3s delete --config cluster_config.yaml This will delete all the resources in the Hetzner Cloud project created by `hetzner-k3s` directly. -**NOTE:** at the load balancers and persistent volumes created by deploying your applications must be deleted manually. This may be addressed in a future release. +**NOTE:** the load balancers and persistent volumes created by deploying your applications must be deleted manually. This may be addressed in a future release. Also note that being able to delete a cluster requires setting `protect_against_deletion` to `true` and that you enter the name of the cluster when you run the `delete` command to confirm that you really want to delete it. These measures are to prevent accidental deletion of a cluster that is jot meant to be deleted. \ No newline at end of file From 358398ce152f7ab3b356b2d1dee8ce4390e9bc96 Mon Sep 17 00:00:00 2001 From: Vito Botta Date: Mon, 3 Feb 2025 20:00:12 +0200 Subject: [PATCH 4/6] Update Deleting_a_cluster.md --- docs/Deleting_a_cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Deleting_a_cluster.md b/docs/Deleting_a_cluster.md index 31151700..cf85fa14 100644 --- a/docs/Deleting_a_cluster.md +++ b/docs/Deleting_a_cluster.md @@ -10,4 +10,4 @@ This will delete all the resources in the Hetzner Cloud project created by `hetz **NOTE:** the load balancers and persistent volumes created by deploying your applications must be deleted manually. This may be addressed in a future release. -Also note that being able to delete a cluster requires setting `protect_against_deletion` to `true` and that you enter the name of the cluster when you run the `delete` command to confirm that you really want to delete it. These measures are to prevent accidental deletion of a cluster that is jot meant to be deleted. \ No newline at end of file +Also note that being able to delete a cluster requires setting `protect_against_deletion` to `false` and that you enter the name of the cluster when you run the `delete` command to confirm that you really want to delete it. These measures are to prevent accidental deletion of a cluster that is jot meant to be deleted. \ No newline at end of file From c5c79d49c1ddfdc660d8a9b837fe49938a2032fb Mon Sep 17 00:00:00 2001 From: Vito Botta Date: Mon, 3 Feb 2025 20:00:39 +0200 Subject: [PATCH 5/6] Update Deleting_a_cluster.md --- docs/Deleting_a_cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Deleting_a_cluster.md b/docs/Deleting_a_cluster.md index cf85fa14..802d01ae 100644 --- a/docs/Deleting_a_cluster.md +++ b/docs/Deleting_a_cluster.md @@ -10,4 +10,4 @@ This will delete all the resources in the Hetzner Cloud project created by `hetz **NOTE:** the load balancers and persistent volumes created by deploying your applications must be deleted manually. This may be addressed in a future release. -Also note that being able to delete a cluster requires setting `protect_against_deletion` to `false` and that you enter the name of the cluster when you run the `delete` command to confirm that you really want to delete it. These measures are to prevent accidental deletion of a cluster that is jot meant to be deleted. \ No newline at end of file +Also note that being able to delete a cluster requires setting `protect_against_deletion` to `false` and that you enter the name of the cluster when you run the `delete` command to confirm that you really want to delete it. These measures are to prevent accidental deletion of a cluster that is not meant to be deleted. \ No newline at end of file From b1af68292e63a0741b80088df58775f3b734701f Mon Sep 17 00:00:00 2001 From: Vito Botta Date: Mon, 3 Feb 2025 20:04:41 +0200 Subject: [PATCH 6/6] Update Creating_a_cluster.md --- docs/Creating_a_cluster.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/Creating_a_cluster.md b/docs/Creating_a_cluster.md index 37393593..106a808f 100644 --- a/docs/Creating_a_cluster.md +++ b/docs/Creating_a_cluster.md @@ -77,7 +77,6 @@ worker_node_pools: # value: value1:NoSchedule - name: medium-autoscaled instance_type: cpx31 - instance_count: 2 location: fsn1 autoscaling: enabled: true