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 new step "Remove manifests and folders that are only needed for bootstrapping cluster so k3s doesn't auto apply on start" produces lots of log output which looks crowded if your terminal is not super-wide:
Proposed Changes
The new step "Remove manifests and folders that are only needed for bootstrapping cluster so k3s doesn't auto apply on start" produces lots of log output which looks crowded if your terminal is not super-wide:
This change condenses the log per loop item down to only the filepath:
Checklist
site.yml
playbookreset.yml
playbook