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 added a Vagrantfile to the vagrant subdirectory. One may create a working environment by the command vagrant up and run the Ansible playbook by the command vagrant provision --provision-with ansible.
I also added a section within the README.md regarding the usage of Vagrant and I made the retry_count in the Verification section of the master role customizeable (default is still 20).
I made the experience, that the ubuntu2110 Box Image of Vagrant is not running into a VirtualBox issue so often than other Ubuntu images do. It still happens from time to time, making the VM unresponsive. It is described here.
timothystewart6
commented
2 years ago
Proposed Changes
I've added a Vagrantfile to the vagrant subdirectory. One may create a working environment by the command
vagrant upand run the Ansible playbook by the commandvagrant provision --provision-with ansible.I also added a section within the README.md regarding the usage of Vagrant and I made the retry_count in the
Verificationsection of the master role customizeable (default is still 20).I made the experience, that the
ubuntu2110Box Image of Vagrant is not running into a VirtualBox issue so often than other Ubuntu images do. It still happens from time to time, making the VM unresponsive. It is described here.Checklist
site.ymlplaybookreset.ymlplaybook