k-andy

Zero friction Kubernetes stack on Hetzner Cloud

This terraform module will install a High Availability K3s Cluster with Embedded DB in a private network on Hetzner Cloud. The following resources are provisionised by default (20€/mo):

• 3x Control-plane: CX11, 2GB RAM, 1VCPU, 20GB NVMe, 20TB Traffic.
• 2x Worker: CX21, 4GB RAM, 2VCPU, 40GB NVMe, 20TB Traffic.
• Network: Private network with one subnet.
• Server and agent nodes are distributed across 3 Datacenters (nbg1, fsn1, hel1) for high availability.

Note: Are you looking for the next generation API Developer Platform? 🔎 Have a look at: WunderGraph Turn your services, databases and 3rd party APIs into a secure unified API in just a few minutes. 🪄

What is K3s?

K3s is a lightweight certified kubernetes distribution. It's packaged as single binary and comes with solid defaults for storage and networking but we replaced local-path-provisioner with hetzner CSI-driver and klipper load-balancer with hetzner Cloud Controller Manager. The default ingress controller (traefik) has been disabled.

Hetzner Cloud integration:

• Preinstalled CSI-driver for volume support.
• Preinstalled Cloud Controller Manager for Hetzner Cloud for Load Balancer support.

Auto-K3s-Upgrades

Enable the upgrade-controller (enable_upgrade_controller = true) and specify your target k3s version (upgrade_k3s_target_version). See here for possible versions.

Label the nodes you want to upgrade, e.g. kubectl label nodes core-control-plane-1 k3s-upgrade=true. The concurrency of the upgrade plan is set to 1, so you can also label them all at once. Agent nodes will be drained one by one during the upgrade.

You can label all control-plane nodes by using kubectl label nodes -l node-role.kubernetes.io/control-plane=true k3s-upgrade=true. All agent nodes can be labelled using kubectl label nodes -l !node-role.kubernetes.io/control-plane k3s-upgrade=true.

To remove the label from all nodes you can run kubectl label nodes --all k3s-upgrade-.

After a successful update you can also remove the upgrade controller and the plans again, setting enable_upgrade_controller to false.

Usage

See a more detailed example with walk-through in the example folder.

Inputs

map(object({
    type      = string
    count     = number
    ip_offset = number
    taints    = list(string)
  }))

{
  "default": {
    "count": 2,
    "ip_offset": 33,
    "taints": [],
    "type": "cx21"
  }
}

[
  "nbg1",
  "fsn1",
  "hel1"
]

Outputs

Common Operations

Agent server replacement (common case)

If you need to cycle an agent, you can do that with a single node following this procedure. Replace the group name and number with the server you want to recreate!

Make sure you drain the nodes first.

kubectl drain that-agent
terraform taint 'module.my_cluster.module.agent_group["GROUP_NAME"].random_pet.agent_suffix[1]'
terraform apply

This will recreate the agent in that group on next apply.

Sophisticated agent server replacement

If you did some weird config change or recreate them by changing the base k3s version in the terraform configuration and terraform wants to replace all your agents at once you can do this. Replacing all by one is probably not a good idea.

Example for replacement of one agent (the first one of that group):

kubectl drain that-agent
terragrunt taint 'module.agent_group["GROUP_NAME"].random_pet.agent_suffix[0]'
terraform apply --target='module.agent_group["GROUP_NAME"].hcloud_server.agent["#0"]' --target='module.agent_group["GROUP_NAME"].hcloud_server_network.agent["#0"]' --target='module.agent_group["GROUP_NAME"].random_pet.agent_suffix[0]'

Control Plane server replacement

Control plane servers do not get recreated when the user-data for cloud-init changes. If you want to recreate one after you changed something which would change the cloud-init you need to taint them.

Primary server

If you for some reason need to replace the primary control plane, you'll need to tell it to join the others.

Set the variable control_plane_primary_index to one of the other control plane nodes (e.g. 2 or 3). Also set control_plane_already_initialized to true so it won't run a cluster-init again. This will make the primary connect to control-plane 2 or 3 after recreation.

Secondary servers

This is how you can replace the servers which didn't initialize the cluster.

terraform taint 'module.my_cluster.hcloud_server.control_plane["#1"]'
terraform apply

Auto-Upgrade

Prerequisite

Install the system-upgrade-controller in your cluster.

KUBECONFIG=kubeconfig.yaml kubectl apply -f ./upgrade/controller.yaml

Upgrade procedure

1. Mark the nodes you want to upgrade (The script will mark all nodes).

KUBECONFIG=kubeconfig.yaml kubectl label --all node k3s-upgrade=true

2. Run the plan for the servers.

KUBECONFIG=kubeconfig.yaml kubectl apply -f ./upgrade/server-plan.yaml

Warning: Wait for completion before you start upgrading your agents.

3. Run the plan for the agents.

KUBECONFIG=kubeconfig.yaml kubectl apply -f ./upgrade/agent-plan.yaml

Backups

K3s will automatically backup your embedded etcd datastore every 12 hours to /var/lib/rancher/k3s/server/db/snapshots/. You can reset the cluster by pointing to a specific snapshot.

1. Stop the master server.

sudo systemctl stop k3s

2. Restore the master server with a snapshot

./k3s server \
  --cluster-reset \
  --cluster-reset-restore-path=<PATH-TO-SNAPSHOT>

Warning: This forget all peers and the server becomes the sole member of a new cluster. You have to manually rejoin all servers.

3. Connect you with the different servers. Backup and delete /var/lib/rancher/k3s/server/db on each server.

sudo systemctl stop k3s
rm -rf /var/lib/rancher/k3s/server/db
sudo systemctl start k3s

This will rejoin the server one after another. After some time, all servers should be in sync again. Run kubectl get node to verify it.

Info: It exists no official tool to automate the procedure. In future, rancher might provide an operator to handle this (issue).

Debugging

Cloud init logs can be found on the remote machines in:

• /var/log/cloud-init-output.log
• /var/log/cloud-init.log
• journalctl -u k3s.service -e last logs of the server
• journalctl -u k3s-agent.service -e last logs of the agent

Credits

• terraform-hcloud-k3s Terraform module which creates a single node cluster.
• terraform-module-k3 Terraform module which creates a k3s cluster, with multi-server and management features.
• Icon created by Freepik from www.flaticon.com