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.
This PR adds a final step to the site.yml playbook, downloading the ~/.kube/config file from the first master to kubekonfig in the playbook directory.
This way you can export KUBECONFIG=${PWD}/kubeconfig, and deploy, reset, deploy, reset, deploy... and never worry about having the right kubeconfig.
I deliberately placed this task in the playbook, it shouldn't be part of a (reusable) role.
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
9 months ago
Proposed Changes
This PR adds a final step to the site.yml playbook, downloading the ~/.kube/config file from the first master to kubekonfig in the playbook directory. This way you can
export KUBECONFIG=${PWD}/kubeconfig, and deploy, reset, deploy, reset, deploy... and never worry about having the right kubeconfig. I deliberately placed this task in the playbook, it shouldn't be part of a (reusable) role.Checklist
site.ymlplaybookreset.ymlplaybook