|
|
|
|
|
by ph4te
1166 days ago
|
|
I've gone through this a few times recently and have it in my homelab and at the office. What works good for me using kube-vip to a VIP on the control plane, and then MetalLB to dish out private addresses in the respective networks, or even statically assigned addresses. I have been turning them all up with k3sup which works like a charm. turn up the first node, install kube-vip, switch config to point to the vip, turn up all my other master nodes, then turn up my workers, install metallb, setup my subnet, install rancher, expose it with a LB, install longhorn. then start deploying things. here is an example of what i use to turn up the first one with k3sup. all of the servers are turned up and configured with ansible doing minimal updates, users, sudo access, etc.. k3sup install \
--ip=192.168.1.11 \
--user=k3s-user \
--sudo \
--tls-san=192.168.1.10 \
--cluster \
--k3s-channel=stable \
--k3s-version=v1.24.12+k3s1 \
--no-extras \
--k3s-extra-args "--flannel-iface=ens160 --node-ip=192.168.1.11" \
--merge \
--local-path $HOME/.kube/config \
--context=k3s-lab |
|