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.
Instructions were unclear on how to have the Kube config copied. As a noob, I spent a considerable amount of time figuring out where the config file was and why the proposed scp debian@master_ip:~/.kube/config ~/.kube/config was giving me no such file error. So, I thought I would help the next home labber by including these updated instructions.
Updated to include the new location for kube config
Added possible errors and how to overcome them
Steps to do after copying the config
I acknowledge that I might be an edge case where the .kube/config file was not deployed in the proper place, but in case this is the new design the PR is here to help out!
Checklist
[ ] Tested locally
[ ] Ran site.yml playbook
[ ] Ran reset.yml playbook
[x] Did not add any unnecessary changes
[ ] Ran pre-commit install at least once before committing
[x] 🚀
Since it is just documentation I will not rerun the site.yml as it is picky!
Proposed Changes
Instructions were unclear on how to have the Kube config copied. As a noob, I spent a considerable amount of time figuring out where the config file was and why the proposed
scp debian@master_ip:~/.kube/config ~/.kube/configwas giving me no such file error. So, I thought I would help the next home labber by including these updated instructions.I acknowledge that I might be an edge case where the .kube/config file was not deployed in the proper place, but in case this is the new design the PR is here to help out!
Checklist
site.ymlplaybookreset.ymlplaybookSince it is just documentation I will not rerun the site.yml as it is picky!