-
k3s-ansible
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. (by techno-tim)
-
keepalived-ingress-vip
:heartbeat: HA/IP failover solution for on-premises and bare-metal Kubernetes clusters.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I'm having a hard time understanding how to setup the network/cluster for HA. I've basically been following along with this guide: https://docs.technotim.live/posts/k3s-etcd-ansible/ which uses MetalLB + kube-vip. I have the cluster running and have the MetalLB IP range set for a block of internal LAN IPs / Layer 2 (unsure if this is correct for what I'm looking to do). All of this seems to be working internally. My confusion is how to get WAN traffic in.
With the VIP on the nodes routes, I presume this is what the kube-vip portion was handling in the original tutorial I was following? Or something like this: https://github.com/janeczku/keepalived-ingress-vip