The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
I have the exact same nucs as you as yourself and the following config
[master]
10.0.0.201
10.0.0.202
10.0.0.203
[node]
10.0.0.201
10.0.0.202
10.0.0.203
# only required if proxmox_lxc_configure: true
# must contain all proxmox instances that have a master or worker node
# [proxmox]
[k3s_cluster:children]
master
node
I am getting the following error on the last step
TASK [k3s/node : Enable and check K3s service] *******************************************************************************************************************
fatal: [10.0.0.201]: FAILED! => {"changed": false, "msg": "Unable to start service k3s-node: Job for k3s-node.service failed because the control process exited with error code.\nSee \"systemctl status k3s-node.service\" and \"journalctl -xeu k3s-node.service\" for details.\n"}
fatal: [10.0.0.202]: FAILED! => {"changed": false, "msg": "Unable to start service k3s-node: Job for k3s-node.service failed because the control process exited with error code.\nSee \"systemctl status k3s-node.service\" and \"journalctl -xeu k3s-node.service\" for details.\n"}
fatal: [10.0.0.203]: FAILED! => {"changed": false, "msg": "Unable to start service k3s-node: Job for k3s-node.service failed because the control process exited with error code.\nSee \"systemctl status k3s-node.service\" and \"journalctl -xeu k3s-node.service\" for details.\n"}
In the logs it seems to be this error which is causing it
Error starting load balancer: listen tcp 127.0.0.1:6444: bind: address already in use
I have the exact same nucs as you as yourself and the following config
I am getting the following error on the last step
In the logs it seems to be this error which is causing it
Hardware:
Intel NUCs