From 136cdb5ecdb7246ae85763c54252bf3bd137ae76 Mon Sep 17 00:00:00 2001 From: Karim Naufal Date: Wed, 27 Apr 2022 09:27:57 +0200 Subject: [PATCH] tweaked readme --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/README.md b/README.md index 6415be5..7e87f03 100644 --- a/README.md +++ b/README.md @@ -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 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" { +
+ +Use in Terraform cloud + +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". + +
+ ## 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.