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.
The IP adress provided as apiserver_endpoint should get assigned to the master node as vIP. Nodes can register to this IP as Kubernetes API.
Current Behavior
The installation fails at the step TASK [k3s/master : Verify that all nodes actually joined (check k3s-init.service if this fails)] ***
I do not see the IP provided as apiserver_endpoint anywhere getting assigned to.
Do I need multi-master setup to get a vIP assigned?
Steps to Reproduce
Setup 3 Ubuntu 20.04 VMs
Assign 1 VM as Master and 2 VMs as Nodes
Assign a IP in the same subnet as the 3 VMs as apiserver_endpoint
Run the playbook as documented
Context (variables)
Operating system: Ubuntu 20.04
Hardware: VMs on AMD Ryzen 7 4900G on a Proxmox hypervisor
Since the vIP for the master node does not getting assigned, the nodes cannot register to a master. So the Kubernetes cluster stays a single master cluster.
Expected Behavior
The IP adress provided as
apiserver_endpoint
should get assigned to the master node as vIP. Nodes can register to this IP as Kubernetes API.Current Behavior
The installation fails at the step
TASK [k3s/master : Verify that all nodes actually joined (check k3s-init.service if this fails)] ***
I do not see the IP provided asapiserver_endpoint
anywhere getting assigned to. Do I need multi-master setup to get a vIP assigned?Steps to Reproduce
apiserver_endpoint
Context (variables)
Operating system: Ubuntu 20.04
Hardware: VMs on AMD Ryzen 7 4900G on a Proxmox hypervisor
Variables Used:
all.yml
Hosts
host.ini
Possible Solution
Since the vIP for the master node does not getting assigned, the nodes cannot register to a master. So the Kubernetes cluster stays a single master cluster.