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.
Following PR #191 , I am proposing new feature to be added, although this slightly customize this project adding a none essentially feature it is very useful mechanism.
I proposed to add kured workload as part of the default configuration. kured watches for the presence of a reboot sentinel i.e.: /var/run/reboot-required and allows to configure how nodes should be reboot as desired. The kured docs is extensive and allows all sort of complexe use case but essentially it a usefule way to control how nodes reboots without creating too much chaos and potential downtime.
For instance, kured can automated cordon and drains worker nodes before reboot and uncordoning them after which typically requires some kubectl-fu ninja skill. kured automated all that as per the configuration rules set.
Add kured manifest
I have not added any post configuration since each use case is unique.
Finally, there are plenty of cool ways to integrate kured into prometheus, slack and other means of notification since again this is individual to each installation.
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
Following PR #191 , I am proposing new feature to be added, although this slightly customize this project adding a none essentially feature it is very useful mechanism.
I proposed to add kured workload as part of the default configuration. kured watches for the presence of a reboot sentinel i.e.:
/var/run/reboot-requiredand allows to configure how nodes should be reboot as desired. The kured docs is extensive and allows all sort of complexe use case but essentially it a usefule way to control how nodes reboots without creating too much chaos and potential downtime.For instance, kured can automated cordon and drains worker nodes before reboot and uncordoning them after which typically requires some
kubectl-fu ninjaskill. kured automated all that as per the configuration rules set.Finally, there are plenty of cool ways to integrate kured into prometheus, slack and other means of notification since again this is individual to each installation.
Checklist
site.ymlplaybookreset.ymlplaybook