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 have noticed working with this repo that I often end up adding more manifest and "goodies" features into it. Splitting manifest into individual files simplify adding new feature or debugging specific workload.
Move kube-vip manifest into individual files
Move metallb manifest and pool config into individual files
I am not checking "Did not add any unnecessary changes" since this could be consider unnecessary.
If this approach is approved, I plan to add more feature like longhorn, kured and others
As requested, I am creating individual PR for each new "add-on" to separated task approach. I've also figure out what was wrong with my linting issue.
Checklist
[X] Tested locally
[X] Ran site.yml playbook
[X] Ran reset.yml playbook
[ ] Did not add any unnecessary changes
[X] Ran pre-commit install at least once before committing
timothystewart6
commented
1 year ago
Proposed Changes
I have noticed working with this repo that I often end up adding more manifest and "goodies" features into it. Splitting manifest into individual files simplify adding new feature or debugging specific workload.
As requested, I am creating individual PR for each new "add-on" to separated task approach. I've also figure out what was wrong with my linting issue.
Checklist
site.ymlplaybookreset.ymlplaybook