Files
homelab-v/tofu/kubernetes/talos/machine-config/common.yaml.tftpl
T
Vegard Hagen 3d68e49d4d fix(tofu): allow multiple nodes on the same host again
A bug reported in #299 resulted in it not being possible to schedule two Talos nodes on the same host machine with the same schematic ID and image version

This commit fixes #299

Signed-off-by: Vegard Hagen <[email protected]>
2025-06-09 21:21:41 +02:00

33 lines
1.3 KiB
Plaintext

machine:
kubelet:
image: ghcr.io/siderolabs/kubelet:${kubernetes_version}
${indent(4, kubelet)}
nodeLabels:
topology.kubernetes.io/region: ${cluster_name}
topology.kubernetes.io/zone: ${node_name}
network:
hostname: ${hostname}
sysctls:
fs.inotify.max_user_watches: 1048576 # Watchdog
fs.inotify.max_user_instances: 8192 # Watchdog
net.core.default_qdisc: fq # 10Gb/s
net.core.rmem_max: 67108864 # 10Gb/s | Cloudflared / QUIC
net.core.wmem_max: 67108864 # 10Gb/s | Cloudflared / QUIC
net.ipv4.tcp_congestion_control: bbr # 10Gb/s
net.ipv4.tcp_fastopen: 3 # Send and accept data in the opening SYN packet
net.ipv4.tcp_mtu_probing: 1 # 10Gb/s | Jumbo frames
net.ipv4.tcp_rmem: 4096 87380 33554432 # 10Gb/s
net.ipv4.tcp_wmem: 4096 65536 33554432 # 10Gb/s
net.ipv4.tcp_window_scaling: 1 # 10Gb/s
vm.nr_hugepages: 1024 # PostgreSQL
cluster:
apiServer:
image: registry.k8s.io/kube-apiserver:${kubernetes_version}
controllerManager:
image: registry.k8s.io/kube-controller-manager:${kubernetes_version}
proxy:
image: registry.k8s.io/kube-proxy:${kubernetes_version}
scheduler:
image: registry.k8s.io/kube-scheduler:${kubernetes_version}