Cluster Creation – Das Kubernetes Cluster DIY Pt. 4

illustration zweier Bildschirme bei der Kubernetes Cluster Creation

Nach den Vorbereitungen in den letzten Kapiteln beschäftigen wir uns nun mit der eigentlichen Erstellung des Clusters.  Am besten folgt ihr der Anleitung dieses kube-hetzner-Projekts auf GitHub.

Hier sind ein paar Änderungen, die ich am Code vorgenommen habe und für die ich einen Pull Request erstellen sollte:

  • dotenv Unterstützung

  • Terraform-Zustandsverfolgung über Google Cloud

  • aktiviertes traefik dashboard

    • großartig zum Debuggen von Middlewares

locals {
# You have the choice of setting your Hetzner API token here or define the TF_VAR_hcloud_token env
# within your shell, such as such: export TF_VAR_hcloud_token=xxxxxxxxxxx 
# If you choose to define it in the shell, this can be left as is.
# Your Hetzner token can be found in your Project > Security > API Token (Read & Write is required).
hcloud_token = data.dotenv.config.env.HCLOUD_TOKEN
resource "google_storage_bucket" "default" {
project       = "REDACTED"
name          = "REDACTED"
force_destroy = false
location      = "EU"
storage_class = "STANDARD"
versioning {
enabled = true
module "kube-hetzner" {
providers = {
hcloud = hcloud
hcloud_token = var.hcloud_token != "" ? var.hcloud_token : local.hcloud_token
# Then fill or edit the below values. Only the first values starting with a * are obligatory; the rest can remain with their default values, or you
# could adapt them to your needs.
# * For local dev, path to the git repo
# source = "../../kube-hetzner/"
# If you want to use the latest master branch
# source = ""
# For normal use, this is the path to the terraform registry
source = "kube-hetzner/kube-hetzner/hcloud"
# You can optionally specify a version number
# version = "1.2.0"
# Note that some values, notably "location" and "public_key" have no effect after initializing the cluster.
# This is to keep Terraform from re-provisioning all nodes at once, which would lose data. If you want to update
# those, you should instead change the value here and manually re-provision each node. Grep for "lifecycle".
# Customize the SSH port (by default 22)
# ssh_port = 2222
# * Your ssh public key
# ssh_public_key = file("~/.ssh/")
ssh_public_key = file(data.dotenv.config.env.SSH_PUBLIC_KEY)
# * Your private key must be "ssh_private_key = null" when you want to use ssh-agent for a Yubikey-like device authentification or an SSH key-pair with a passphrase.
# For more details on SSH see
# ssh_private_key = file("~/.ssh/id_ed25519")
ssh_private_key = file(data.dotenv.config.env.SSH_PRIVATE_KEY)
# You can add additional SSH public Keys to grant other team members root access to your cluster nodes.
# ssh_additional_public_keys = []
# You can also add additional SSH public Keys which are saved in the hetzner cloud by a label.
# See
# ssh_hcloud_key_label = "role=admin"
# If you use SSH agent and have issues with SSH connecting to your nodes, you can increase the number of auth tries (default is 2)
# ssh_max_auth_tries = 10
# If you want to use an ssh key that is already registered within hetzner cloud, you can pass its id.
# If no id is passed, a new ssh key will be registered within hetzner cloud.
# It is important that exactly this key is passed via `ssh_public_key` & `ssh_private_key` vars.
# hcloud_ssh_key_id = ""
# These can be customized, or left with the default values
# * For Hetzner locations see
network_region = "eu-central" # change to `us-east` if location is ash
# If you must change the network CIDR you can do so below, but it is highly advised against.
# network_ipv4_cidr = ""
# If you must change the cluster CIDR you can do so below, but it is highly advised against.
# Cluster CIDR must be a part of the network CIDR!
# cluster_ipv4_cidr = ""
# For the control planes, at least three nodes are the minimum for HA. Otherwise, you need to turn off the automatic upgrades (see README).
# **It must always be an ODD number, never even!** Search the internet for "splitbrain problem with etcd" or see
# For instance, one is ok (non-HA), two is not ok, and three is ok (becomes HA). It does not matter if they are in the same nodepool or not! So they can be in different locations and of various types.
# Of course, you can choose any number of nodepools you want, with the location you want. The only constraint on the location is that you need to stay in the same network region, Europe, or the US.
# For the server type, the minimum instance supported is cpx11 (just a few cents more than cx11); see
# IMPORTANT: Before you create your cluster, you can do anything you want with the nodepools, but you need at least one of each, control plane and agent.
# Once the cluster is up and running, you can change nodepool count and even set it to 0 (in the case of the first control-plane nodepool, the minimum is 1).
# You can also rename it (if the count is 0), but do not remove a nodepool from the list.
# The only nodepools that are safe to remove from the list are at the end. That is due to how subnets and IPs get allocated (FILO).
# You can, however, freely add other nodepools at the end of each list if you want. The maximum number of nodepools you can create combined for both lists is 255.
# Also, before decreasing the count of any nodepools to 0, it's essential to drain and cordon the nodes in question. Otherwise, it will leave your cluster in a bad state.
# Before initializing the cluster, you can change all parameters and add or remove any nodepools. You need at least one nodepool of each kind, control plane, and agent.
# The nodepool names are entirely arbitrary, you can choose whatever you want, but no special characters or underscore, and they must be unique; only alphanumeric characters and dashes are allowed.
# If you want to have a single node cluster, have one control plane nodepools with a count of 1, and one agent nodepool with a count of 0.
# Please note that changing labels and taints after the first run will have no effect. If needed, you can do that through Kubernetes directly.
# ⚠️ When choosing ARM cax* server types, for the moment they are only available in fsn1.
# Muli-architecture clusters are OK for most use cases, as container underlying images tend to be multi-architecture too.
# * Example below:
control_plane_nodepools = [
name        = "control-plane-fsn1",
server_type = "cpx11",
location    = "fsn1",
labels      = [],
taints      = [],
count       = 1
# Enable automatic backups via Hetzner (default: false)
backups = true
# {
#   name        = "control-plane-nbg1",
#   server_type = "cpx11",
#   location    = "nbg1",
#   labels      = [],
#   taints      = [],
#   count       = 1
#   # Enable automatic backups via Hetzner (default: false)
#   # backups = true
# },
# {
#   name        = "control-plane-hel1",
#   server_type = "cpx11",
#   location    = "hel1",
#   labels      = [],
#   taints      = [],
#   count       = 1
#   # Enable automatic backups via Hetzner (default: false)
#   # backups = true
# }
# labels are used for autoscaler
# Just use nodeName within kubernetes.
agent_nodepools = [
name        = "payload-agent-large",
server_type = "cpx31",
location    = "fsn1",
labels      = [
taints      = [],
count       = 1
# Enable automatic backups via Hetzner (default: false)
backups = true
name        = "watchdog-agent-large",
server_type = "cpx31",
location    = "fsn1",
labels      = [
taints      = [],
count       = 1
# Enable automatic backups via Hetzner (default: false)
backups = true
name        = "butler-agent-medium",
server_type = "cpx21",
location    = "fsn1",
labels      = [
taints      = [],
count       = 1
# Enable automatic backups via Hetzner (default: false)
backups = true
# {
#   name        = "storage",
#   server_type = "cpx21",
#   location    = "fsn1",
#   # Fully optional, just a demo.
#   labels      = [
#     ""
#   ],
#   taints      = [],
#   count       = 1
#   # In the case of using Longhorn, you can use Hetzner volumes instead of using the node's own storage by specifying a value from 10 to 10000 (in GB)
#   # It will create one volume per node in the nodepool, and configure Longhorn to use them.
#   # Something worth noting is that Volume storage is slower than node storage, which is achieved by not mentioning longhorn_volume_size or setting it to 0.
#   # So for something like DBs, you definitely want node storage, for other things like backups, volume storage is fine, and cheaper.
#   # longhorn_volume_size = 20
#   # Enable automatic backups via Hetzner (default: false)
#   # backups = true
# },
# Egress nodepool useful to route egress traffic using Hetzner Floating IPs (
# used with Cilium's Egress Gateway feature
# See the for an example use case.
# {
#   name        = "egress",
#   server_type = "cpx11",
#   location    = "fsn1",
#   labels = [
#     ""
#   ],
#   taints = [
#     ""
#   ],
#   floating_ip = true
#   count = 1
# },
# Arm based nodes, currently available only in FSN location
# {
#   name        = "agent-arm-small",
#   server_type = "cax11",
#   location    = "fsn1",
#   labels      = [],
#   taints      = [],
#   count       = 1
# }
# Add custom control plane configuration options here.
# E.g to enable monitoring for etcd, proxy etc:
# control_planes_custom_config = {
#  etcd-expose-metrics = true,
#  kube-controller-manager-arg = "bind-address=",
#  kube-proxy-arg ="metrics-bind-address=",
#  kube-scheduler-arg = "bind-address=",
# }
# You can enable encrypted wireguard for the CNI by setting this to "true". Default is "false".
# FYI, Hetzner says "Traffic between cloud servers inside a Network is private and isolated, but not automatically encrypted." 
# Source:
# It works with all CNIs that we support.
# Just note, that if Cilium with cilium_values, the responsability of enabling of disabling Wireguard falls on you.
# enable_wireguard = true
# * LB location and type, the latter will depend on how much load you want it to handle, see
load_balancer_type     = "lb11"
load_balancer_location = "fsn1"
### The following values are entirely optional (and can be removed from this if unused)
# You can refine a base domain name to be use in this form of nodename.base_domain for setting the reserve dns inside Hetzner
# base_domain = ""
# Cluster Autoscaler
# Providing at least one map for the array enables the cluster autoscaler feature, default is disabled
# By default we set a compatible version with the default initial_k3s_channel, to set another one,
# have a look at the tag value in
# ⚠️ Based on how the autoscaler works with this project, you can only choose either x86 instances or ARM server types for ALL autocaler nodepools.
# Also, as mentioned above, for the time being ARM cax* instances are only available in fsn1.
# If you are curious, it's ok to have a multi-architecture cluster, as most underlying container images are multi-architecture too.
# * Example below:
# autoscaler_nodepools = [
#   {
#     name        = "autoscaled-small"
#     server_type = "cpx21"
#     location    = "fsn1"
#     min_nodes   = 0
#     max_nodes   = 5
#   }
# ]
# Enable etcd snapshot backups to S3 storage.
# Just provide a map with the needed settings (according to your S3 storage provider) and backups to S3 will
# be enabled (with the default settings for etcd snapshots).
# Cloudflare's R2 offers 10GB, 10 million reads and 1 million writes per month for free.
# For proper context, have a look at
# etcd_s3_backup = {
#   etcd-s3-endpoint        = ""
#   etcd-s3-access-key      = "<access-key>"
#   etcd-s3-secret-key      = "<secret-key>"
#   etcd-s3-bucket          = "k3s-etcd-snapshots"
# }
# To enable Hetzner Storage Box support, you can enable csi-driver-smb, default is "false".
# enable_csi_driver_smb = true
# To use local storage on the nodes, you can enable Longhorn, default is "false".
# See a full recap on how to configure agent nodepools for longhorn here
# Also see Longhorn best practices here
# enable_longhorn = false
# By default, longhorn is pulled from
# If you need a version of longhorn which assures compatibility with rancher you can set this variable to 
# longhorn_repository = ""
# The namespace for longhorn deployment, default is "longhorn-system".
# longhorn_namespace = "longhorn-system"
# The file system type for Longhorn, if enabled (ext4 is the default, otherwise you can choose xfs).
# longhorn_fstype = "xfs"
# how many replica volumes should longhorn create (default is 3).
# longhorn_replica_count = 1
# When you enable Longhorn, you can go with the default settings and just modify the above two variables OR you can add a longhorn_values variable
# with all needed helm values, see towards the end of the file in the advanced section.
# If that file is present, the system will use it during the deploy, if not it will use the default values with the two variable above that can be customized.
# After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.
# Also, you can choose to use a Hetzner volume with Longhorn. By default, it will use the nodes own storage space, but if you add an attribute of
# longhorn_volume_size (⚠️ not a variable, just a possible agent nodepool attribute) with a value between 10 and 10000 GB to your agent nodepool definition, it will create and use the volume in question.
# See the agent nodepool section for an example of how to do that.
# To disable Hetzner CSI storage, you can set the following to "true", default is "false".
# disable_hetzner_csi = true
# If you want to use a specific Hetzner CCM and CSI version, set them below; otherwise, leave them as-is for the latest versions.
# hetzner_ccm_version = ""
# hetzner_csi_version = ""
# If you want to specify the Kured version, set it below - otherwise it'll use the latest version available.
# kured_version = ""
# If you want to enable the Nginx ingress controller ( instead of Traefik, you can set this to "nginx". Default is "traefik".
# By the default we load optimal Traefik and Nginx ingress controller config for Hetzner, however you may need to tweak it to your needs, so to do,
# we allow you to add a traefik_values and nginx_values, see towards the end of this file in the advanced section.
# After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.
# If you want to disable both controllers set this to "none"
# ingress_controller = "nginx"
# You can change the number of replicas for selected ingress controller here. The default 0 means autoselecting based on number of agent nodes (1 node = 1 replica, 2 nodes = 2 replicas, 3+ nodes = 3 replicas)
# ingress_replica_count = 1
# Use the klipperLB (similar to metalLB), instead of the default Hetzner one, that has an advantage of dropping the cost of the setup.
# Automatically "true" in the case of single node cluster (as it does not make sense to use the Hetzner LB in that situation).
# It can work with any ingress controller that you choose to deploy.
# Please note that because the klipperLB points to all nodes, we automatically allow scheduling on the control plane when it is active.
# enable_klipper_metal_lb = "true"
# If you want to configure additional arguments for traefik, enter them here as a list and in the form of traefik CLI arguments; see
# They are the options that go into the additionalArguments section of the Traefik helm values file.
# Example: traefik_additional_options = ["--log.level=DEBUG", "--tracing=true"]
traefik_additional_options = ["--api", "--api.dashboard=true", "--api.insecure=true"]
# By default traefik is configured to redirect http traffic to https, you can set this to "false" to disable the redirection.
# traefik_redirect_to_https = false
# If you want to disable the metric server set this to "false". Default is "true".
# enable_metrics_server = false
# If you want to allow non-control-plane workloads to run on the control-plane nodes, set this to "true". The default is "false".
# True by default for single node clusters, and when enable_klipper_metal_lb is true. In those cases, the value below will be ignored.
# allow_scheduling_on_control_plane = true
# If you want to disable the automatic upgrade of k3s, you can set below to "false".
# Ideally, keep it on, to always have the latest Kubernetes version, but lock the initial_k3s_channel to a kube major version,
# of your choice, like v1.25 or v1.26. That way you get the best of both worlds without the breaking changes risk.
# For production use, always use an HA setup with at least 3 control-plane nodes and 2 agents, and keep this on for maximum security.
# The default is "true" (in HA setup i.e. at least 3 control plane nodes & 2 agents, just keep it enabled since it works flawlessly).
# automatically_upgrade_k3s = false
# The default is "true" (in HA setup it works wonderfully well, with automatic roll-back to the previous snapshot in case of an issue).
# IMPORTANT! For non-HA clusters i.e. when the number of control-plane nodes is < 3, you have to turn it off.
# automatically_upgrade_os = false
# If you need more control over kured and the reboot behaviour, you can pass additional options to kured.
# For example limiting reboots to certain timeframes. For all options see:
# The default options are: `--reboot-command=/usr/bin/systemctl reboot --pre-reboot-node-labels=kured=rebooting --post-reboot-node-labels=kured=done --period=5m`
# Defaults can be overridden by using the same key.
# kured_options = {
#   "reboot-days": "su"
#   "start-time": "3am"
#   "end-time": "8am"
#   "time-zone": "Local"
# }
# Allows you to specify either stable, latest, testing or supported minor versions.
# see and
# ⚠️ If you are going to use Rancher addons for instance, it's always a good idea to fix the kube version to latest - 0.01,
# ⚠️ Rancher currently only supports v1.25 and earlier versions:
# The default is "v1.26".
# initial_k3s_channel = "stable"
# The cluster name, by default "k3s"
# cluster_name = ""
# Whether to use the cluster name in the node name, in the form of {cluster_name}-{nodepool_name}, the default is "true".
# use_cluster_name_in_node_name = false
# Extra k3s registries. This is useful if you have private registries and you want to pull images without additional secrets.
# Or if you want to proxy registries for various reasons like rate-limiting.
# It will create the registries.yaml file, more info here
# Note that you do not need to get this right from the first time, you can update it when you want during the life of your cluster.
# The default is blank.
/* k3s_registries = <<-EOT
- ""
username: username
password: password
EOT */
# Additional environment variables for the host OS on which k3s runs. See for example . 
# additional_k3s_environment = {
#   "CONTAINERD_HTTP_PROXY" : "http://your.proxy:port",
#   "CONTAINERD_HTTPS_PROXY" : "http://your.proxy:port",
#   "NO_PROXY" : ",,",
# }
# Additional commands to execute on the host OS before the k3s install, for example fetching and installing certs.
# preinstall_exec = [
#   "curl https://somewhere.over.the.rainbow/ca.crt > /root/ca.crt",
#   "trust anchor --store /root/ca.crt",
# ]
# Additional flags to pass to the k3s server command (the control plane).
# k3s_exec_server_args = "--kube-apiserver-arg enable-admission-plugins=PodTolerationRestriction,PodNodeSelector"
# If you want to allow all outbound traffic you can set this to "false". Default is "true".
# restrict_outbound_traffic = false
# Adding extra firewall rules, like opening a port
# More info on the format here
extra_firewall_rules = [
description     = "Allow Outbound SMTP"
direction       = "out"
protocol        = "tcp"
port            = "465"
source_ips      = ["", "::/0"]
destination_ips = [] # Won't be used for this rule
# {
#   description = "To Allow ArgoCD access to resources via SSH"
#   direction       = "out"
#   protocol        = "tcp"
#   port            = "22"
#   source_ips      = [] # Won't be used for this rule
#   destination_ips = ["", "::/0"]
# }
# If you want to configure a different CNI for k3s, use this flag
# possible values: flannel (Default), calico, and cilium
# As for Cilium, we allow infinite configurations via helm values, please check the CNI section of the readme over at
# Also, see the cilium_values at towards the end of this file, in the advanced section.
# cni_plugin = "cilium"
# You can choose the version of Calico that you want. By default, the latest is used.
# More info on available versions can be found at
# Please note that if you are getting 403s from Github, it's also useful to set the version manually. However there is rarely a need for that!
# calico_version = "v3.25.0"
# If you want to disable the k3s default network policy controller, use this flag!
# Both Calico and Ciliun cni_plugin values override this value to true automatically, the default is "false".
# disable_network_policy = true
# If you want to disable the automatic use of placement group "spread". See
# We advise to not touch that setting, unless you have a specific purpose.
# The default is "false", meaning it's enabled by default.
# placement_group_disable = true
# By default, we allow ICMP ping in to the nodes, to check for liveness for instance. If you do not want to allow that, you can. Just set this flag to true (false by default).
# block_icmp_ping_in = true
# You can enable cert-manager (installed by Helm behind the scenes) with the following flag, the default is "true".
# Will be installed with butler helm chart
enable_cert_manager = false
# IP Addresses to use for the DNS Servers, set to an empty list to use the ones provided by Hetzner, defaults to ["", "", ""].
# The number of different DNS servers is limited to 3 by Kubernetes itself.
# dns_servers = []
# When this is enabled, rather than the first node, all external traffic will be routed via a control-plane loadbalancer, allowing for high availability.
# The default is false.
# use_control_plane_lb = true
# Let's say you are not using the control plane LB solution above, and still want to have one hostname point to all your control-plane nodes.
# You could create multiple A records of to let's say pointing to all of your control-plane nodes ips.
# In which case, you need to define that hostname in the k3s TLS-SANs config to allow connection through it. It can be hostnames or IP addresses.
# additional_tls_sans = [""]
# Oftentimes, you need to communicate to the cluster from inside the cluster itself, in which case it is important to set this value, as it will configure the hostname
# at the load balancer level, and will save you from many slows downs when initiating communications from inside. Later on, you can point your DNS to the IP given
# to the LB. And if you have other services pointing to it, you are also free to create CNAMES to point to it, or whatever you see fit.
# If set, it will apply to either ingress controllers, Traefik or Ingress-Nginx.
# lb_hostname = ""
# You can enable Rancher (installed by Helm behind the scenes) with the following flag, the default is "false".
# ⚠️ Rancher currently only supports Kubernetes v1.25 and earlier, you will need to set initial_k3s_channel to a supported version:
# When Rancher is enabled, it automatically installs cert-manager too, and it uses rancher's own self-signed certificates.
# See for options
# The easiest thing is to leave everything as is (using the default rancher self-signed certificate) and put Cloudflare in front of it.
# As for the number of replicas, by default it is set to the numbe of control plane nodes.
# You can customized all of the above by adding a rancher_values variable see at the end of this file in the advanced section.
# After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.
# IMPORTANT: Rancher's install is quite memory intensive, you will require at least 4GB if RAM, meaning cx21 server type (for your control plane).
# ALSO, in order for Rancher to successfully deploy, you have to set the "rancher_hostname".
# enable_rancher = true
# If using Rancher you can set the Rancher hostname, it must be unique hostname even if you do not use it.
# If not pointing the DNS, you can just port-forward locally via kubectl to get access to the dashboard.
# If you already set the lb_hostname above and are using a Hetzner LB, you do not need to set this one, as it will be used by default.
# But if you set this one explicitly, it will have preference over the lb_hostname in rancher settings.
# rancher_hostname = ""
# When Rancher is deployed, by default is uses the "latest" channel. But this can be customized.
# The allowed values are "stable" or "latest".
# rancher_install_channel = "stable"
# Finally, you can specify a bootstrap-password for your rancher instance. Minimum 48 characters long!
# If you leave empty, one will be generated for you.
# (Can be used by another rancher2 provider to continue setup of rancher outside this module.)
# rancher_bootstrap_password = ""
# Separate from the above Rancher config (only use one or the other). You can import this cluster directly on an
# an already active Rancher install. By clicking "import cluster" choosing "generic", giving it a name and pasting
# the cluster registration url below. However, you can also ignore that and apply the url via kubectl as instructed
# by Rancher in the wizard, and that would register your cluster too.
# More information about the registration can be found here
# rancher_registration_manifest_url = ""
# Extra values that will be passed to the `extra-manifests/kustomization.yaml.tpl` if its present.
# extra_kustomize_parameters={}
# It is best practice to turn this off, but for backwards compatibility it is set to "true" by default.
# See
# When "false". The kubeconfig file can instead be created by executing: "terraform output --raw kubeconfig > cluster_kubeconfig.yaml"
# Always be careful to not commit this file!
create_kubeconfig = true
# Don't create the kustomize backup. This can be helpful for automation.
# create_kustomization = false
### ADVANCED - Custom helm values for packages above (search _values if you want to located where those are mentioned upper in this file)
# ⚠️ Inside the _values variable below are examples, up to you to find out the best helm values possible, we do not provide support for customized helm values.
# Please understand that the indentation is very important, inside the EOTs, as those are proper yaml helm values.
# We advise you to use the default values, and only change them if you know what you are doing!
# Cilium, all Cilium helm values can be found at
# The following is an example, please note that the current indentation inside the EOT is important.
/*   cilium_values = <<EOT
mode: kubernetes
devices: "eth1"
requireIPv4PodCIDR: true
kubeProxyReplacement: strict
l7Proxy: false
enabled: true
type: wireguard
EOT */
# Cert manager, all cert-manager helm values can be found at
# The following is an example, please note that the current indentation inside the EOT is important.
/*   cert_manager_values = <<EOT
installCRDs: true
replicaCount: 3
replicaCount: 3
replicaCount: 3
EOT */
# csi-driver-smb, all csi-driver-smb helm values can be found at
# The following is an example, please note that the current indentation inside the EOT is important.
/*   csi_driver_smb_values = <<EOT
name: csi-smb-controller
replicas: 1
runOnMaster: false
runOnControlPlane: false
memory: 300Mi
cpu: 10m
memory: 20Mi
memory: 100Mi
cpu: 10m
memory: 20Mi
memory: 200Mi
cpu: 10m
memory: 20Mi
EOT */
# Longhorn, all Longhorn helm values can be found at
# The following is an example, please note that the current indentation inside the EOT is important.
/*   longhorn_values = <<EOT
defaultDataPath: /var/longhorn
defaultFsType: ext4
defaultClassReplicaCount: 3
defaultClass: true
EOT */
# Traefik, all Traefik helm values can be found at
# The following is an example, please note that the current indentation inside the EOT is important.
/*   traefik_values = <<EOT
replicas: 1
globalArguments: []
enabled: true
type: LoadBalancer
"": "k3s"
"": "true"
"": "true"
"": "nbg1"
"": "lb11"
"": "true"
redirectTo: websecure
EOT */
# Nginx, all Nginx helm values can be found at
# You can also have a look at, to understand how it works, and all the options at your disposal.
# The following is an example, please note that the current indentation inside the EOT is important.
/*   nginx_values = <<EOT
watchIngressWithoutClass: "true"
kind: "DaemonSet"
"use-forwarded-headers": "true"
"compute-full-forwarded-for": "true"
"use-proxy-protocol": "true"
"": "k3s"
"": "true"
"": "true"
"": "nbg1"
"": "lb11"
"": "true"
EOT */
# Rancher, all Rancher helm values can be found at
# The following is an example, please note that the current indentation inside the EOT is important.
/*   rancher_values = <<EOT
source: "rancher"
hostname: ""
replicas: 1
bootstrapPassword: "supermario"
EOT */
provider "hcloud" {
token = var.hcloud_token != "" ? var.hcloud_token : local.hcloud_token
provider "kubernetes" {
config_path = "~/.kube/config"
terraform {
required_version = ">= 1.3.3"
backend "gcs" {
bucket  = "REDACTED" 
prefix  = "REDACTED"
required_providers {
hcloud = {
source  = "hetznercloud/hcloud"
version = ">= 1.38.2"
dotenv = {
source  = "jrhouston/dotenv"
version = "~> 1.0"
output "kubeconfig" {
value     = module.kube-hetzner.kubeconfig
sensitive = true
data "dotenv" "config" {
# NOTE there must be a file called `dev.env` in the same directory as the .tf config
filename = ".env"
variable "hcloud_token" {
sensitive = true
default   = ""


In dieser Kubernetes-Serie haben wir uns mit verschiedenen Aspekten der Verwaltung von containerisierten Anwendungen und deren effizienter Orchestrierung beschäftigt. Wir sind in die Welt von Kubernetes eingetaucht, haben seine leistungsstarken Funktionen entdeckt und Einblicke in seine Kernkomponenten gewonnen. Nun, da wir uns dem Ende dieser Serie nähern, ist es an der Zeit, über das Gelernte nachzudenken und unsere nächsten Schritte zu skizzieren.

Mein Ziel war es, euch eine solide Grundlage für die effektive Verwaltung von containerisierten Anwendungen zu vermitteln. Ich hoffe sehr, dass mir das gelungen ist! Außerdem möchte ich euch dazu ermutigen, euch auf dem Laufenden zu halten & das Thema weiter zu verfolgen. Beteiligt euch an bestehenden Erweiterungsprojekten, erstellt eigene Helm-Diagramme und priorisiert die Verfügbarkeit eurer Deployments!

illustration von servern

Wenn ihr meine Empfehlungen beherzigt und weiterhin das sich ständig weiterentwickelnde Kubernetes-Ökosystem im Auge behaltet, werdet ihr gut gerüstet sein um

  • eure Deployments zu optimieren

  • widerstandfähige Applikationen auszuliefern und

  • immer vorne mit dabei zu sein, wenn es um Container-Orchestrierung geht!

Viel Spaß beim Kuberneten!


PS: Ich plane eine Fortsetzung, die sich mit hochverfügbaren Clustern und Storage beschäftigt! Folgt gerne unseren Social Media Kanälen und bleibt immer up to date!

Links & further reading:

Picture of Alptuğ Dingil

Alptuğ Dingil

Alptuğ unterstützt uns bereits seit 2022 im Bereich Softwareentwicklung. Neben den Kundenprojekten sucht er immer wieder nach neuen Herausforderungen und beschäftigte sich in jüngster Zeit mit Kubernetes und der Konfiguration eines DIY-Clusters. Außerdem ließ er sich von Google als Professional Cloud Architect zertifizieren.

Kürzliche Posts

illustration von chatbots

Advanced ChatGPT

Die Nutzung des Tools für Fortgeschrittene Der OpenAI Playground (dt. Spielwiese/Spielplatz) ist ein mächtiges Werkzeug, das es Nutzer/-innen und Produktteams

Read More »