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.
In its current form, the playbook cannot manage dual-stack multi-master clusters. The reason for this is every master other than the first get a URL parameter which includes k3s_node_ip of the first master verbatim. Since k3s_node_ip contains multiple, comma-separated IP addresses in dual-stack clusters, we need to extract a single IP address here.
Checklist
[x] Tested locally
[x] Ran site.yml playbook
[x] Ran reset.yml playbook
[x] Did not add any unnecessary changes
[x] Ran pre-commit install at least once before committing
timothystewart6
commented
1 year ago
Proposed Changes
In its current form, the playbook cannot manage dual-stack multi-master clusters. The reason for this is every master other than the first get a URL parameter which includes
k3s_node_ipof the first master verbatim. Sincek3s_node_ipcontains multiple, comma-separated IP addresses in dual-stack clusters, we need to extract a single IP address here.Checklist
site.ymlplaybookreset.ymlplaybook