kjuulh/terraform-hcloud-kube-hetzner
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

tweaked readme

Browse Source
This commit is contained in:
Karim Naufal 2022-04-27 09:27:57 +02:00
parent a356122b2d
commit 136cdb5ecd
No known key found for this signature in database
GPG Key ID: 9CB4A7C28C139CA5
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -137,6 +137,13 @@ _To turn off k3s upgrades, you can either remove the `k3s_upgrade=true` label or
kubectl -n system-upgrade label node <node-name> k3s_upgrade-
```
Alternatively, you can disable the k3s automatic upgrade without individually editing the labels on the nodes. Instead you can just delete the two system controller upgrade plans with:
```sh
kubectl delete plan k3s-agent -n system-upgrade
kubectl delete plan k3s-server -n system-upgrade
```
### Individual Components Upgrade
Rarely needed, but can be handy in the long run. During the installation, we automatically download a backup of the kustomization to a `kustomization_backup.yaml` file. You will find it next to your `kubeconfig.yaml` at the root of your project.
@ -212,6 +219,14 @@ module "kube-hetzner" {
</details>
<details>
<summary>Use in Terraform cloud</summary>
To use Kube-Hetzner on Terraform cloud, use as a Terraform module as mentioned above, but also change the "execution-mode" from "remote" to "local".
</details>
## Debugging
First and foremost, it depends, but it's always good to have a quick look into Hetzner quickly without logging in to the UI. That is where the `hcloud` cli comes in.