Skip to content

Commit

Permalink
Merge branch 'main' of github.com:vitobotta/hetzner-k3s
Browse files Browse the repository at this point in the history
  • Loading branch information
vitobotta committed Feb 3, 2025
2 parents f4454de + b1af682 commit 52f7dff
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
1 change: 0 additions & 1 deletion docs/Creating_a_cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,6 @@ worker_node_pools:
# value: value1:NoSchedule
- name: medium-autoscaled
instance_type: cpx31
instance_count: 2
location: fsn1
autoscaling:
enabled: true
Expand Down
3 changes: 2 additions & 1 deletion docs/Deleting_a_cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:** 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 not meant to be deleted.
2 changes: 1 addition & 1 deletion docs/Masters_in_different_locations.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 52f7dff

Please sign in to comment.