K3s installation steps

[kube-vip]

K3s installation steps

[thebsdbox]

This is now added to the documentation.

[alexellis]

Docker isn't usually installed to k3s hosts, that's part of the beauty and speed of the solution..

Therefore it'd be nice if you had the equivalent of the below:

sudo docker run --network host --rm plndr/kube-vip:0.1.8 kubeadm init --interface ens160 --vip $VIP --arp --leaderElection | sed 's/name: kube-vip/name: kube-vip-'hostname'/g' | sed 's/path: \/etc\/kubernetes\/admin.conf/path: \/etc\/rancher\/k3s\/k3s.yaml/g' | sudo tee /var/lib/rancher/k3s/server/manifests/vip.yaml

But that ran as a static binary or a bash file.

When we spoke, you had a concern of the size of your binary. You could publish a tiny binary to do this one task, that'd be the easiest to maintain and a clean approach, you could hack some bash, or zip your binary.. zipping for us reduced the size of inletsctl from 30-35mb to 10mb. https://github.com/inlets/inletsctl/releases

[alexellis]

Keep up the good work. I'm looking forward to telling people about Kube-vip for a HA k3s control plane IP.

[thebsdbox]

These steps need an alternative method that doesn't involve the Docker engine. Perhaps curl -sFL kube-vip.io/k3sManifest.yaml | sed 's/old_IP/new_IP/' > manifest.yaml

[thebsdbox]

Right, here we go !

Option one:

curl -sL kube-vip.io/k3s | vipAddress=192.168.0.10 vipInterface=ens192 sh > /var/lib/rancher/k3s/server/manifests/vip.yaml

Option two:

export vipAddress=192.168.0.10
export vipInterface=ens192
curl -sL kube-vip.io/k3s | sh > /var/lib/rancher/k3s/server/manifests/vip.yaml