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.
I've noticed I messed up in the last commit regarding the http_proxy setup.
On nodes/workers/agents it should've put the http_proxy config in the k3s-node.service.d dir, instead it puts it in k3s.service.d.
This fixes that slip-up.
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
Proposed Changes
I've noticed I messed up in the last commit regarding the http_proxy setup. On nodes/workers/agents it should've put the http_proxy config in the
k3s-node.service.d
dir, instead it puts it ink3s.service.d
. This fixes that slip-up.Checklist
site.yml
playbookreset.yml
playbook